05:06 pm - sparkymark - Java Web Start problem after upgrade to 1.4.2_05 After a mouseslip this morning, I managed to overwrite jarsigner.exe in my 1.4.2_04 SDK with a zero byte file.I took the opportunity to download SDK _05, used the provied jarsigner to signe the application I wanted to ship with Java Web Start, and uploaded it to my web site www.earthprime.org.But now I can't run the application: on running 1.4.2_05 Java Web Start (or for that matter the 1.4.2_04 copy I still have installed) I am warned that my signing can't be trusted and that the application requires unrestricted access to the local system and network: this is normal, and as usual I click "Start" to install it.My application can access the network for two main reasons, to download configuration data from my site, www.earthprime.org, or to read e-mail from a configured location: in this case the configured location is pop.oneandone.co.uk. The first of these operations succeeded, the second fails with a Java.security.AccessControlException.So I seem to have ended up with my application "sandboxed", only able initiate connections to the site it was downloaded from. I stress that I agreed to give the application unrestricted access to the system. 1. Has something changed in the latest JRE to make this so?2. How can I revert my default JRE to 1.4.2_04 so I can at least see it working again?3. Is there something wrong with my jnlp file Here that has gone undetected in prior SDK versions? Warning You may want to right click and save that link to avoid initiating an installation of my software. The jnlp file has worked fine for me for months. Is it complaining because I have the offline-allowed tag set, for example?edit The unofficial JWS FAQ says to escape the sandbox in a signed app, use System.setSecurityManager(null). I've never had to use that before though. Could that be it?edit Adding that line to "main" fixed the problem...leaving one remaining question. WTF? If this is really a change to Java Web Start that has occurred between minor JRE releases, how many applications will break? If it was just me, how did I get away with it for so long?
sparkymark - Java Web Start problem after upgrade to 1.4.2_05 After a mouseslip this morning, I managed to overwrite jarsigner.exe in my 1.4.2_04 SDK with a zero byte file.I took the opportunity to download SDK _05, used the provied jarsigner to signe the application I wanted to ship with Java Web Start, and uploaded it to my web site www.earthprime.org.But now I can't run the application: on running 1.4.2_05 Java Web Start (or for that matter the 1.4.2_04 copy I still have installed) I am warned that my signing can't be trusted and that the application requires unrestricted access to the local system and network: this is normal, and as usual I click "Start" to install it.My application can access the network for two main reasons, to download configuration data from my site, www.earthprime.org, or to read e-mail from a configured location: in this case the configured location is pop.oneandone.co.uk. The first of these operations succeeded, the second fails with a Java.security.AccessControlException.So I seem to have ended up with my application "sandboxed", only able initiate connections to the site it was downloaded from. I stress that I agreed to give the application unrestricted access to the system. 1. Has something changed in the latest JRE to make this so?2. How can I revert my default JRE to 1.4.2_04 so I can at least see it working again?3. Is there something wrong with my jnlp file Here that has gone undetected in prior SDK versions? Warning You may want to right click and save that link to avoid initiating an installation of my software. The jnlp file has worked fine for me for months. Is it complaining because I have the offline-allowed tag set, for example?edit The unofficial JWS FAQ says to escape the sandbox in a signed app, use System.setSecurityManager(null). I've never had to use that before though. Could that be it?edit Adding that line to "main" fixed the problem...leaving one remaining question. WTF? If this is really a change to Java Web Start that has occurred between minor JRE releases, how many applications will break? If it was just me, how did I get away with it for so long?