Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 1.10, resource properties missing #587

Closed
bjorndarri opened this issue Jun 4, 2024 · 5 comments
Closed

Version 1.10, resource properties missing #587

bjorndarri opened this issue Jun 4, 2024 · 5 comments

Comments

@bjorndarri
Copy link

Resource properties are not forwarded to the application since updating to 1.10.

Looks like all my applications are broken with this update, since they all have jdbc urls specified in the resource section.

I'm working with very simple jnlp files, here's an example:

<?xml version="1.0" encoding="utf-8"?>
<jnlp spec="1.0+" codebase="https://xxxxx.yyy/app/" href="application.jnlp">

  <information>
    <offline-allowed/>
  </information>

  <security>
    <all-permissions/>
  </security>

  <resources>
    <j2se version="11+"/>
    <jar href="application.jar"/>
    <property name="db.url" value="jdbc:oracle:thin:@xxxxx.yyyy.zz:1234:rrrr"/>
  </resources>
  
  <application-desc main-class="xx.xx.xx.ApplicationPanel"/>
</jnlp>

The system property db.url is no longer forwarded to the application. There's nothing in the log file, by the way.

I looked through recent commits and found an interesting line in this one: cce96c6

OwsJvmLauncher:250

env.put(ApplicationInstance.IGNORE_JNLP_RESOURCE_PROPERTIES, "true");

I haven't looked into this any further, but this line does look a bit suspect, given the problem I'm running into :-).

@fleminra
Copy link
Contributor

fleminra commented Jun 7, 2024

+1

All of our Web Start applications that depend on JNLP-set properties are fatally broken in OWS 1.10.0.

1.9.1 works.

@patrice0
Copy link

patrice0 commented Jun 7, 2024

I've had the same problem.

@sclassen
Copy link
Member

sclassen commented Jun 7, 2024

We found the source of the problem an plan on releasing a bugfix early next week

@patrice0
Copy link

patrice0 commented Jun 7, 2024

Thank you!

@sclassen
Copy link
Member

Fixed with 1.10.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants