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?
RE: Auto Reload Features by Tomcat
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]
Re: Auto Reload Features by Tomcat
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
Re: Auto Reload Features by Tomcat
I think it's because that you just enabled the Auto Build feature of eclipse, so every time you changed your java source, eclipse built it for you, and tomcat saw the class files changed and then reloaded that context. But when you metioned for my production, I guess that machine do not have an eclipse and you just replaced the java source without compiling it to /WEB-INF/classes and thus tomcat won't reload your context. Did I get it? 2006/6/2, ks.foong [EMAIL PROTECTED]: 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]
RE: Auto Reload Features by Tomcat
If I understand correctly, you are describing moving a src file (ProfileServlet.java) under project/WEB-INF/src in your production Tomcat webapps directory. I know that am not sure why you believe that Tomcat will automatically compile your servlet source (I believe it will for a .jsp file) The context parameter reloadable is defined as: Set to true if you want Catalina to monitor classes in /WEB-INF/classes/ and /WEB-INF/lib for changes, and automatically reload the web application if a change is detected. This feature is very useful during application development, but it requires significant runtime overhead and is not recommended for use on deployed production applications. ... It does not mention the source/src directory at all. I assume you are on the most current version of Tomcat, 5.5 - but the reloadable attribute was available in prior versions also. HTH - Richard -Original Message- From: ks.foong [mailto:[EMAIL PROTECTED] Sent: Friday, June 02, 2006 1:52 AM 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]
