P4
We are experiencing some issues related to launching JavaFX apps via Web Start that need to be addressed:
1. We're noticing an anomaly with JRE 6 update 13 launching Java Web Start programs. The user is told that the JAR files weren't signed by the same signer, when in fact they were. Installing update 14 or later makes this symptom disappear.
2. A user that has JRE 6 update 13 that requests an update is told that they already have the latest version, so the problem in the previous point is not self correcting. Shouldn't the automatic updates ensure that the latest version (e.g. JRE 6 update 17) is installed as a result?
On a related note, one can specify in the JNLP file that the user must have JRE 6 to run the app, but I haven't had any success trying to specify the required update (e.g. update 17). I have done some research, but haven't found an answer that works for me. Here is the related line in the JNLP file that I've been using:
3. There is a flag in the JNLP (Java Web Start) files that provides for background loading (running the app first and checking for updates on the next go). We are not setting that flag, so I suspect that the URL (that ends in jnlp) is being cached by the browser. Attached is the JNLP file.
<j2se version="1.6+" initial-heap-size="256m" max-heap-size="512m"/>
These issues will cause unnecessary deployment issues for our customer's users.
1. We're noticing an anomaly with JRE 6 update 13 launching Java Web Start programs. The user is told that the JAR files weren't signed by the same signer, when in fact they were. Installing update 14 or later makes this symptom disappear.
2. A user that has JRE 6 update 13 that requests an update is told that they already have the latest version, so the problem in the previous point is not self correcting. Shouldn't the automatic updates ensure that the latest version (e.g. JRE 6 update 17) is installed as a result?
On a related note, one can specify in the JNLP file that the user must have JRE 6 to run the app, but I haven't had any success trying to specify the required update (e.g. update 17). I have done some research, but haven't found an answer that works for me. Here is the related line in the JNLP file that I've been using:
3. There is a flag in the JNLP (Java Web Start) files that provides for background loading (running the app first and checking for updates on the next go). We are not setting that flag, so I suspect that the URL (that ends in jnlp) is being cached by the browser. Attached is the JNLP file.
<j2se version="1.6+" initial-heap-size="256m" max-heap-size="512m"/>
These issues will cause unnecessary deployment issues for our customer's users.