My Java 7 Smart Client users are getting a warning when launching the client stating this app will be blocked in a future Java update. See the yellow box in the image below:
[attachment=1]Screen Shot 2013-10-24 at 9.43.46 AM.png[/attachment]
Clicking “More Information” leads to this dialog of information. Note that I circled the problem text:
[attachment=0]Screen Shot 2013-10-24 at 9.43.57 AM.png[/attachment]
How are we to handle this as it’s my understanding that the app’s JNLP file is generated on the fly when the user hits the download link?
It sounds like the Smart Client will be blocked without a JNLP signature in the future for those using Java 7.
if you remove the extra -XX property set as avm argument in the servoy-admin page, you will not get the message, about that the jnlp is not signed.
There is now another issue with Java 7 update 45, complaining about a missing Application Name attribute.
Patrick Talbot is working on this one, to set this attribute with the signtester!
yes that’s the one I was talking about.
In newer versions of Servoy, you have to replace it with a ‘space’ or else if you make it empty and hit save, Servoy puts is default back.
It’s a setting that keeps objects longer in memory, and reduces traffic a bit (as Johan explained me)
We are running a few weeks now, without this setting, and don’t see much performance difference.
But please try & check in you own current setup.
If you use for example the browser-suite bean, you can’t remove the other settings in there, because else the browser-suite won’t run.
But than you have to accept indeed the jnlp signing warning. Servoy can’t do a thing about that, because the jnlp is totally dynamic generated!
I’m not using the browser-suite, so I’ve completely cleared those arguments with a ‘space’ as you suggested. I’m still receiving the exact same message in the yellow box in my original post. I’ve cleared the java cache, restarted the server after clearing the arguments and downloaded a new JNLP file after the server restart. Same results.
