Reputation: 20581
How I can force updating of my jar
files when client open applet application? Jar files always cached in client machine. And I always need to clear cache using Java Control Panel.
Upvotes: 1
Views: 2596
Reputation: 2701
Version your jars in your applet tag with each build / deploy. This will force a reload.
ARCHIVE="foo-1.0.16.jar" > ARCHIVE="foo-1.0.17.jar"
Upvotes: 0
Reputation: 75376
If your problem is that old versions of the files are present after redeploying new versions, then consider having a form of timestamps or build numbers in your jar file names.
This will require you to update your JNLP file for every deployment, but your cache problems should go away. It did for us.
Upvotes: 0
Reputation: 168825
I always need to clear cache using Java Control Panel.
This is probably because the JWS client does not recognize the Jars as being new. One source of such confusion lies in the difference in time-zone between the developers machine and that of the server. In that case, the Jars will typically update within the next 24 hours.
For the purposes of testing, do it outside a browser.
Upvotes: 1