Hey Greg,
Turns out my clocks weren't synchronized. Once I synchronized the
clocks, everything started working...
Go figure.
Thanks,
Matt
-----Original Message-----
From: java-dev-bounces+mweiss=email@hidden
[mailto:java-dev-bounces+mweiss=email@hidden] On Behalf Of
Greg Guerin
Sent: Monday, May 22, 2006 6:03 PM
To: email@hidden
Subject: Re: Updating java web start application
Matt Weiss wrote:
>I have an application that consist of a few jars and the jnlp file. I
>want to update the .jnlp file, adding an additional jar. No matter
>what I do, I cannot get webstart to load the new jnlp file from the
>URL. It always uses the local cached jnlp file.
Is the application locally stored and locally launched, i.e. a saved
Desktop Application launched off-line? If so, then I don't think it
will automatically update. I think you have to manually update it in
JWS. As I recall, this is considered a feature, not a bug.
If the application is launched "online" (i.e. triggered by the reception
of a jnlp file), you need to confirm exactly what's being transferred
(if
anything) for each relevant resource/file.
First, you need to eliminate the web-server itself as complicit. If you
update a file on the web-server, but it doesn't correctly detect the
modification-date, then all subsequent GET requests of that resource
with an If-Modified-Since header will never see that the resource has
changed, so will never retrieve it again, and will continue using the
locally cached resource.
One way to confirm the server is acting correctly is to use the 'curl'
command to get the URL of the jnlp file, and use the '-D file' option to
write the returned headers to a separate file. Then confirm that the
dates stated for the resource match what they should be. You can also
use 'curl'
to produce an If-Modified-Since header in the request, to see if that
works correctly, too. See 'man curl'.
If the web-server looks like it's working correctly, you next need to
look at the jnlp file that's received. You probably need to do a
"before" and "after" trial with two different files, so you can see
whether the two retrieved resources really are different. If they are,
then the "after"
file should be the one that's being handed off to Java Web Start.
Eventually, you might end up having to use Java Cache Viewer.app, or
Java Web Start.app, depending on which version of the JVM the app is
running under on each client.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
