WAR files don't unpack if the webapp is already there
I'm going through the standard compile-edit-test look on some applications using JBuilder and Tomcat right now. I've got JBuilder creating a new WAR file in TOMCAT_HOME/webapps on rebuild, but I need to delete the old webapp directory before Tomcat will notice the new one and unpack it. Is this a feature of Tomcat? Shouldn't it notice if the webapp directory is out of date in comparison to the WAR file? James -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: WAR files don't unpack if the webapp is already there
It's a feature. Sucks, huh? - Original Message - From: James Turner [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 09, 2002 2:23 PM Subject: WAR files don't unpack if the webapp is already there I'm going through the standard compile-edit-test look on some applications using JBuilder and Tomcat right now. I've got JBuilder creating a new WAR file in TOMCAT_HOME/webapps on rebuild, but I need to delete the old webapp directory before Tomcat will notice the new one and unpack it. Is this a feature of Tomcat? Shouldn't it notice if the webapp directory is out of date in comparison to the WAR file? James -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: WAR files don't unpack if the webapp is already there
Older versions of Tomcat don't, new ones will if you set reloadable to true in the context. It will monitor WEB-ING/lib and WEB-INF/classes for changes and reload if it detects any. This canj cause a performance degradation on your server so you may only want to do this for development. Rick - Original Message - From: James Turner [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 09, 2002 3:23 PM Subject: WAR files don't unpack if the webapp is already there I'm going through the standard compile-edit-test look on some applications using JBuilder and Tomcat right now. I've got JBuilder creating a new WAR file in TOMCAT_HOME/webapps on rebuild, but I need to delete the old webapp directory before Tomcat will notice the new one and unpack it. Is this a feature of Tomcat? Shouldn't it notice if the webapp directory is out of date in comparison to the WAR file? James -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: WAR files don't unpack if the webapp is already there
Not sure what you mean by new ones, but TC 4.0.3 does NOT unpack wars if the directory already exists regardless of the reloadable flag. Jeff - Original Message - From: Rick Fincher [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, May 09, 2002 2:57 PM Subject: Re: WAR files don't unpack if the webapp is already there Older versions of Tomcat don't, new ones will if you set reloadable to true in the context. It will monitor WEB-ING/lib and WEB-INF/classes for changes and reload if it detects any. This canj cause a performance degradation on your server so you may only want to do this for development. Rick - Original Message - From: James Turner [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 09, 2002 3:23 PM Subject: WAR files don't unpack if the webapp is already there I'm going through the standard compile-edit-test look on some applications using JBuilder and Tomcat right now. I've got JBuilder creating a new WAR file in TOMCAT_HOME/webapps on rebuild, but I need to delete the old webapp directory before Tomcat will notice the new one and unpack it. Is this a feature of Tomcat? Shouldn't it notice if the webapp directory is out of date in comparison to the WAR file? James -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
