Until recently, when I changed and recompiled a JavaBean,
Tomcat 3.2.1 (properly) invalidated my session, and 
automagically picked up the changes the next session.

Now, I have to restart Tomcat to get the changes, which
puts a serious crimp in the development cycle.

I *think* the event which changed this behaviour was when
the UNIX box was rebooted, but Tomcat was not properly
shut down beforehand.

My question is:

   How can I get Tomcat to again incorporate a changed 
   bean without shutting down and restarting Tomcat?

--Glenn

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to