Submitted On 18-SEP-2008
PaulDBrown
This is even more serious than I thought. With no network connection, the application can *NOT* be launched offline even from the Java Cache Viewer - contrary to what I had indicated in my earlier bug report (where I was launching it in 'offline' mode but actually still had the network connection). To me this is a 'showstopper' with respect to Java Web Start applications - they *cannot* be launched offline.
Submitted On 19-SEP-2008
dserodio
Ugh! Bad bug
Submitted On 21-OCT-2008
sacke
This is a disaster for our company. We love Java Web Start with all the stuff you get for free like automatic updates, etc. But it's a requirement that the apps can be be started offline as our users/client use our app in the field.
I see the bug is closed, but is it dismissed or is anyone working on a fix? To me this seems like a huuuuge show stopper for Java Web Start!
Submitted On 22-OCT-2008
sacke
I found a resolution for my problem. Changing the shortcut element attribute from:
<shortcut online="true">
to
<shortcut online="false">
enable our Java Web Start app to run offline. Tested successfully on JRE 1.6.0_10-b33 and 1.6.0_03-b05.
Submitted On 18-NOV-2008
PaulDBrown
This bug is reported as being fixed and yet with the latest released version of java 6 update 10, web start applications can still not be launched from a windows command line using:
javaws -offline http://localhost/myapp.jnlp
They now fail with the message:
CouldNotLoadArgumentException[ Could not load file/URL specified: http://localhost/myapp.jnlp]
Presumably that's because, as mentioned in the Evaluation, I am referring to the application with the full URL but how else am I to reference it? By the name alone doesn't work either.
Please reopen this bug - it is *NOT* fixed.
Thanks.
-Paul
Submitted On 16-DEC-2008
Please reopen this bug since I'm having trouble with running webstart apps offline.
Submitted On 22-DEC-2008
karstrom
Please reopen this bug, this is a showstopper.
Submitted On 22-DEC-2008
karstrom
this works fine on1.6.0_12-ea.
Where is the reference on this fix?
Submitted On 09-APR-2009
Vivekankumar
A Workaround (Hopefully):
Problem is seen when there are directories inside jar's imported into JWS using <nativelib> tag. Either use <jar> tag to import or don't import jar's with directories, using <nativelib>.
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|