On Sep 25, 2008, at 8:32 AM, Sebastian Hagedorn wrote: --On 25. September 2008 08:13:17 -0700 Mike Swingler < email@hidden> wrote: We believe that this is a difference between J2SE 5.0 and Java SE 6.
It seems that way ... On 64-bit Intel machines, all Web Start launching goes though the Java SE
6 deploy.jar and javaws.jar, even if it is targeting an older JVM and set
of runtime classes. On 32-bit capable hardware all Web Start launching
goes though the J2SE 5.0 deploy.jar and javaws.jar.
In the J2SE 5.0 Web Start classes, changes were made to how resources are
loaded from the Web Start cache, which we integrated directly. If
possible, can someone test on Windows to see if this issue reproduces
with the latest version of J2SE 5.0 (not Java SE 6).
I just did. I installed 1.5.0_16 under Windows XP SP 3 and made sure that it's used for JNLP. We show the version that's used in the About Box, so I could verify that it was indeed being used. And it worked fine. So this issue appears to be Mac-only.
We believe we have isolated the pattern that is broken with the 1.5.0_16 webstart. This problem happens when you try to get a new URL to a resource using an existing URL as shown below : URL resourceBase = MyClass.class.getResource("myfile");
URL newURL = new URL(resourceBase, "anotherfile");The workaround it to use Class.getResource instead : URL resourceBase = MyClass.class.getResource("myfile");
URL newURL = MyClass.class.getResource("anotherfile");This works reliably on all platforms and all versions.
Hope this helps, Bino George. Java Runtime Engineer
Apple Inc.
|
