Only one question: why don't you want the webapp to be reloaded?
You can save your sessions easily using the Session Manager (just insert the following in your context.xml: <Manager className="org.apache.catalina.session.StandardManager"/>): http://tomcat.apache.org/tomcat-5.0-doc/config/manager.html On 8/28/06, Hammad Sophie <[EMAIL PROTECTED]> wrote:
Hello. I've searched through and read a number of messages related to 'hot deployment'. All of them deal with hot deploying the ENTIRE webapp, not just particular classes in my webapp. We use tomcat as the application server/container for our application. We use a single production server running a single instance of tomcat on client sites. Frequently we run into a situation where a bug fix must be deployed without restarting tomcat or even reloading the webapp. This works well when a patch contains only JSPs. We simply unzip/copy the jsps into the webapps/blah directory and tomcat recompiles them itself automatically. However, alot of times, our patches also contain our class files [located in webapps/blah/WEB-INF/classes]. Currently we can copy these files to the appropriate directory within tomcat, but they do not get picked up unless tomcat is restarted or the webapp redeployed. Is there any way to 'hot deploy' certain classes within a webapp such that the entire webapp does not reload, but only the new classes are picked up and used? Thanks. Hammad.
-- -=-=-=-=-=-=-=-=-=-=-=-=- Andrés González. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
