HOWEVER, when I move the applet.class file down to temp under WEB-INF, it does not work. I tried various combinations of CODEBASE parameters in the callapplet.html file, but maybe I am missing something - the applet just does not get loaded.
Is there a solution that I am missing or is this a limitation that one has to live with? The reason I am wanting to move the applet.class file down under WEB-INF/classes/temp is to keep all the class files in one place.
Is there an alternative arrangement of directory structure?
Thanks in advance.
[BSouther Edit: added code tags] [ April 18, 2006: Message edited by: Ben Souther ]
Anything you put under the WEB-INF directory will not be directly accessible to the end user, you can only put there "helper-stuff" like your server side classes, libs,...
I guess that an applet needs to be directly available to the end user because, from the server point of view, this is just file that the user agent wants to download. As far as the server is concerned, there is nothing special in the fact that the browser will then execute it. So the root of the web app sounds like a correct place, although I agree it looks messy.
Maybe is there a way to map a ressource from some WEB-INF/applet-ressources/ directory to a public name thanks to the DD ?
It is a mistake to think you can solve any major problems just with potatoes.<br />--Douglas Adams