I remember something about a reloadable parameter in the Server.xml (in a tag above context either host or engine I think) that has that attribute as well. Unless the "override" attribute is included, the attribute in the context tag is not applied. I may be chasing the wrong horse, but it somewhere for you start. check the docs. Also, with tomcat5+ it is recommended that you do not place your context tag in your server.xml but use the new method. read the section on contexts in the docs.
On 6/2/06, ks.foong <[EMAIL PROTECTED]> wrote:
Forget to mentioned, I have make sure my <Context> tag in server.xml have included the reloadable="true" entity <Context path="/project" reloadable="true" ...........> Foong Kim Seong -----Original Message----- From: ks.foong [mailto:[EMAIL PROTECTED] Sent: Friday, June 02, 2006 4:52 PM To: 'Tomcat Users List' Subject: Auto Reload Features by Tomcat Hi, I notice that starting from Tomcat 5 onwards; we can enjoy the benefit of the "Auto-reload" features of it. I personally have tried it with my Eclipse development. Each time I have changed any servlet coding, the eclipse (or more specific, Tomcat) able to detect the changes and Reload for itself. But for my production, I am not sure how this is work. I have replaced my servlet, ProfileServlet.java to the [CATALINA_HOME]/webapps/project/WEB-INF/src/com/servlet folder. I login into my system; I didn't see any changes at all. So, any ideas how can is this reload features work in production machine? Do I need to issues any command for this? --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Marc Farrow
