I have a tomcat 3.3.1 application that I suspect might be caching old class files.
The application consists of about 50 servlet classes (I'm using straight servlets, not JSPs) deployed as a jar file. When I update the jar file, I think some of the old classes are not being replaced w/ the new ones. Will any of the following cause servlet classes to be cached between stop/starts: 1) Not clearing the /work directory. Can this directory have anything to do with servlets being cached? Or does tomcat strictly use it to compile JSPs? 2) Storing old jar files in the WEB-INF/lib with extensions other than .jar. For example, can I rename app.jar to app.jar.20030906 and leave it in WEB-INF/lib along with the new app.jar file, or could this cause servlet caching issues? Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
