-
Enhancement
-
Resolution: Duplicate
-
P5
-
None
-
jaws-1.0
-
x86
-
generic
feedback request from:
Tej Ram <###@###.###>
-----------------------
If you are running on Windows, this behavior could be due to
Windows file locking behavior. If you have a copy of an application
open, then update the application on the web server and re-launch,
Java Web Start will attempt to update the application but fail
because the JAR files are locked by Windows (since a copy of the
app is already running).
I believe there's another bug here also, because Java Web Start
will now think your app has been updated, when it really has not.
We are aware of the problem and we plan to address it in a future
release.
-----------------------
Tej Ram <###@###.###>
-----------------------
If you are running on Windows, this behavior could be due to
Windows file locking behavior. If you have a copy of an application
open, then update the application on the web server and re-launch,
Java Web Start will attempt to update the application but fail
because the JAR files are locked by Windows (since a copy of the
app is already running).
I believe there's another bug here also, because Java Web Start
will now think your app has been updated, when it really has not.
We are aware of the problem and we plan to address it in a future
release.
-----------------------