We have a case where clients seem to be eternally caching versions of applets. We\'re making use of the tag correctly within o
Unfortunately, different versions of the Java Plug-In have different caching behaviors. Setting your Cache-Control and Last-Modified HTTP headers is the ideal solution, but it only works under the most recent versions of the JRE.
The only solution GUARANTEED to work is to rename your application jars when their versions change (we've seen strange caching behavior when trying other tricks like adding query strings based on file dates). This isn't so difficult to do if you have a properly automated deployment system.
As per this link , same jar file should not be listed int "archive" and "cache_archive" params. In that case, the JAR file is cached using the native browser cache.
You can remove applet from Java cache using Java Control Panel
.
For example, on Win XP
Start -> Control Panel -> Java -> Temporary Internet Files[View]