Rob, I know with using ECLIPSE and Tomcat4x you can run 'catalina jpda start' from a command prompt and be able to walk through your servlet code and make changes, recompile and run the updated .java file without having to restart Tomcat. This is very useful in a development environment. I don't see why this would not carry over to Tomcat5. - Duncan
----- Original Message ----- From: "Rob Ross" <[EMAIL PROTECTED]> To: "'Tomcat Users List'" <[EMAIL PROTECTED]> Sent: Tuesday, March 30, 2004 10:55 PM Subject: RE: restarting tomcat > > > -----Original Message----- > > From: Duncan Krebs [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 30, 2004 8:51 PM > > To: Tomcat Users List > > Subject: Re: restarting tomcat > > > > > > I also know that there are different types of debugging modes > > that you can > > run Tomcat it that do not require a restart for a .class file change. > > - Duncan > > Actually, according the Servlet 2.4 spec which I am just starting to read, > this should not be true. > > SRV.3.7 Reloading Considerations (page 33) states ... > > "...any such implementation must ensure that all servlets, and classes that > they may use, are loaded in the scope of a single class loader. This > requirement is needed to guarantee that the application will behave as > expected by the Developer." > > My understanding of this requirement is that there would be no way to reload > a single servlet separately from the other servlets in the same context - a > new Classloader would be created to load the new servlet, and all other > servlets/classes in that context. > > But since I just started reading this, maybe I'm not understanding all the > subtleties. > > Rob > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
