This seems to be a perennial problem. It is very
annoying when you are debugging applets, since
you want to keep reloading the latest version.
Here are some solutions that are found on the web:
If you are stuck while trying to develop
an applet, the simplest way is to use "appletviewer"
instead of a browing.
In Netscape, do shift-reload. In Internet Explorer,
do control-reload. [That is, you hold down the
shift or control key while clicking the reload button]
In the previous step, you may need to also
clear your cache.
According to www.acme.com/java/,
hitting a reload will only reload the html page,
but not the applet. To force this, you must kill
the browser (to stop the Java Virtual Machine), and restart.
Note that www.acme.com has other nice resources related to
Java and applets.
Another source (http://forum.sun.com, Jan 2003)
says that the simplest solution
is to let the applet call it self. Add
a Button called "reloadButton" to the applet,
and register with this button an Actionlistener
with the following method:
public void actionPerformed (ActionEvent e)
{
if (e.getSource().equals(reloadButton))
getAppletContext().showDocument("applet's url here");
}
Someone else suggested directly calling the start() method
of the applet.