Leggendo tutte le risposte, sembra che questa sia stata apprezzata

codice:
 Gandalf_the_black

Hello applet fans.
As you know the solution of putting the jar file in classpath only works for server side programming. When deploying multiple web apps that uses the same applet on multiple pages the problem still exist. However I have found a solution. The trick is to avoid multiple classloaders. And that can be done by controlling the codebase. Each new codebase gives a new classloader. In the Java Console you can list the classloaders (press 'l') and see their code base. To make sure all applets are loaded by the same classloader put the jar archive in a common place on the server and in all applet tags set the codebase attibute to point to this location. E.g. 
<applet name="myApplet"
	code="com.xxx.MyApplet"
	codebase="http://localhost:9080/Common/myapplets"
	archive="http://localhost:9080/Common/myapplets/myarchive.jar" 
	width="350" height="150"	
	mayscript>
	<param name="cabbase" value="/Common/myapplets/myarchive.cab">
</applet>