I has been quite a while since I have used Tomcat 3.3.x. My recollection is that accessing the changed servlet would trigger a reload of the webapp. This differs from the newer Tomcats which have a background thread checking for changes. Also, with a default configuration, I don't recall anything special that was needed beyond setting the context to be reloadable. I can't say why this isn't working for you.
As for the manager, Tomcat came with an admin webapp. However, it never got far enough along to be worthy of its own manual. It's mentioned briefly in the User's Guide, but I think that is about it. If you want a "real" manager/admin webapp, you will need to upgrade to a newer Tomcat. Cheers, Larry > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Frances > Sent: Tuesday, February 28, 2006 12:49 PM > To: users@tomcat.apache.org > Subject: Tomcat 3 -- servlets don't reload.. > > when I make changes to a servlet I don't see changes unless I > turn tomcat off and on... this is a huge pain, it's at work, > where we can't be turning Tomcat off and on all day long > whenever we make changes to a servlet.. Is there a way > around this? (Does Tomcat 3 come with a Manager? I can't > find manager-howto.html among docs (which does come with > Tomcat 5..) many thanks.. > > Frances > > > --------------------------------------------------------------------- > 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]
