• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Applet Versioning

 
David Kafrissen
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Greetings,

Is there a way to version applets?

Problem:
The default behavior of the JVM is to cache applets. When I deploy a new version, in-house, the new applet is not loaded but the cached old applet is, and the tester reports that bug is not fixed, feature is not added etc.

Web Browsers get the correct behavior for html pages, some html is cached, but new pages are loaded.

Solution:
are there some variables in the manifest that the JVM would look at and then auto download the new version when the page is refreshed?
 
James Hodgkiss
Ranch Hand
Posts: 401
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a similar requirement - does anyone know a solution?

Cheers,
James
 
Ulf Dittmer
Rancher
Posts: 42969
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You could make the version number part of the jar file name. So instead of "MyApplet.jar" you'd use MyApplet10.jar, MyApplet11.jar etc. That way its looks like a different file to the browser.
 
David Kafrissen
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thats a good idea and maybe we should have done that.

What we had been doing until now is using the applet tag. While it is officially deprecated it seems to be supported by every browser.

What we are doing is we went to the object tag and using the cache_version attribute. We have the ant script automatically insert the current subversion rev into that string in the html file.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic