0

I have an application overriding the default toolkit, by setting the system.property awt.toolkit. For the standalone application I set this up in the code, by using System.setProperty(String, String). This works just fine. But when I try to run via webstart, the property is set to late, because java already set up the toolkit (for splash or webstart console maybe).

So I added the property to the jnlp, but without any effect. The property is not even passed, to the vm. I figured out, that it is considered "unsecure" by java itself and my applications is considered "untrusted".

see here

For an untrusted application, system properties set in the JNLP file will only be set by Java Web Start if they are considered secure.

I have a signed application with a valid certificate from a certificate authority, but still my application is considered untrusted. i did all the steps suggested here, but without any effect. I don't get any of those dialogs about untrusted application or publisher information anymore, but I still do not get the property passed to my virtual machine.

any ideas, what I could try next?

BTW: still using java 7 as runtime

Community
  • 1
  • 1
tejoe
  • 163
  • 1
  • 14
  • found the following entry. http://stackoverflow.com/questions/19400725/with-java-update-7-45-the-system-properties-no-more-set-from-jnlp-tag-property will try the comment about adding the jnlp to the jar file tomorrow. But as i am using dynamic jnlp (generated by a perl script) this is not really sufficient. – tejoe Oct 09 '14 at 21:54
  • another entry [here](http://stackoverflow.com/questions/19571562/javaws-java-7-update-45-cannot-send-properties?lq=1) confirms that – tejoe Oct 10 '14 at 08:25
  • adding APPLICATION.JNLP to signed jar file did not work. Also see [java documentation for signed jnlp](http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/security/signedJNLP.html) – tejoe Oct 10 '14 at 12:45

0 Answers0