Hi Remy, thanx for you answer. Using the Manager App with start&stop or with reload reloads my Servlet, destroy() and init() are processed. Unfortunatly this does NOT force TC4.0 to reload the web.xml. I think I will have a look at the nighly build...
Regards, Max -----Original Message----- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: Mittwoch, 6. Februar 2002 15:41 To: Tomcat Users List Subject: Re: Tomcat 3.3 and 4.0, different behaviour when reloading the "web.xml" > Hello everyone. > > I'm new to this mailing List, and hopefully I don't bother anyone asking > questions which have already been answered. > > I'm using Tomcat 4.0 standalone on Win2K and Tomcat 3.3 on MPE. I use Tomcat > to run JavaServlets. > > On MPE (it includes an Posix-Shell, behaves similar to Unix), when change > the "web.xml" in the Folder "WEB-INF" Tomcat 3.3 notices this, destroys > every Servlet mentioned in the "web.xml" and if the Servlet gets accessed > again ist is reloaded. Same happens if I only touch the "web.xml". This is > visible becaus of some logging I coded in the init() and the destroy() of > the Servlets. > When do the same on my Win3K machine Tomcat 4.0 does NOT reload the > "web.xml". He does not destroy the classes neither. > > Has anyone an Idea how I can tell Tomcat4.0 to reload the "web.xml"? I want > him to read out the up-to-date Information I wrote into the web.xml. > ...snip... > <context-param> > <param-name>MyParameter</param-name> > <param-value>UseThisParameterValue</param-value> > </context-param> > ...snip... Either: - Use the manager webapp (do a stop followed by a start) - Use a nightly build (4.0-HEAD includes automatic deployment and web.xml tracking) Remy -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
