Depends on the server. I think his problem is that the server is NOT finding the class/jar file.
If he is using a browser to ask for a jsp page, that page is returning an HTML page with an <APPLET tag(or simiilar) to the browser. The browser then asks the server for the class/jar file referenced in that tag.
That's the request I'd like to see the path to the file for. But a server can translate that path to somewhere else, hence my shotgun approach to putting jar files everywhere until the server finds one. Then removing them one by one to find which one is being used.
For example when I load an HTML page (
http://127.0.0.1:8080/Testing/AppletReader.html) into my browser and that HTML has an archive= attribute, my server sees the following to HTTP GETs:
GET /Testing/AppletReader.html HTTP/1.1
GET /Testing/AppletReader.jar HTTP/1.1
The <APPLET tag:
<APPLET CODE=AppletReader Archive=AppletReader.jar WIDTH=300 HEIGHT=300>