I received this from a collegue: ------------------ 6.4 Automatic Servlet Reloading Tomcat 3.2 includes a feature whereby you can ask it to automatically reload servlet classes (loaded from either the WEB-INF/classes directory or a JAR file in the WEB-INF/lib directory) that have been changed. This feature is experimental, and may not be completely functional. In particular, changes to classes other than the servlet you are requesting do not trigger class reloads -- you will need to restart Tomcat to reflect changes in those classes. Reloading is enabled by including a reloadable="true" attribute on the <Context> element in the "conf/server.xml" file. Note that automatic reload support is not recommended for production applications because of its experimental nature, and the extra overhead required to perform the necessary checks on every request. ------------------- Peer Digital, Inc. Jeff Crawford Configuration Manager Senior Software Engineer 4001 Discovery Drive · Suite 270 Boulder, CO 80303 Direct: 303 544-7547 Main: 303 415 3550 Fax: 303 415 3540 www.peerdigital.com -----Original Message----- From: yt [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 03, 2001 4:24 PM To: [EMAIL PROTECTED] Subject: Re: Automatic reloading of modified .jar/.class files If it is enabled by default, how come my classes arenever automatically reloaded when I transfer them over to tomcat ? How do you disable it btw ? I didn't know it impacts performance that much .. Thanks. On 3 Feb 2001, at 14:53, Geoff Lane wrote: > Yes it does, but it is a significant performance impact to enable it > (it's enabled by default). > Tomcat does not (that I know of) have a way of rereading configuration > files on the without a restart though. > > James Bucanek wrote: > > > > Greetings, > > > > I'm a complete newbie to Tomcat. I glanced through the documentation > > and FAQs and didn't find an answer to this. So, now I'll annoy the > > list. ;) > > > > My ISP has just installed Tomcat and I plan to move several servlets > > that have been running under Sun's JSWDK reference server over to it. > > > > One really annoying problem (actually the lack of a feature) under > > the JSWDK server is that the servlet's class loader wasn't smart > > enough to recognized when a .jar or .class file had been modified and > > know to reload those Classes. > > > > The end result was, whenever I made a change to my servlet, I had to > > kill the server and start it up again. Rather rude to those users > > with active sessions! > > > > So, does Tomcat's class loader do this? If not, is there some other > > way of forcing it to reload the servlet code? That is, some way > > accessible to a mere user, and not one that requires root/admin > > privileges? > > > > Thanks in advance, > > > > James > > > > __________________________________ > > James Bucanek > > <mailto:[EMAIL PROTECTED]> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, email: [EMAIL PROTECTED] > > -- > ------------------------------------------- > Geoff Lane <[EMAIL PROTECTED]> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
