2010/9/23 Jason Britton <jbritto...@gmail.com>: > Glad you brought this back up P - was cursing this problem again yesterday. > So if tomcat 6.0.29 is running and my foo webapp is deployed, if I dare copy > in foo.war for auto re-deployment tomcat nukes my foo.xml context definition > in conf/Catalina/HOST/ directory. Absolutely maddening. Is this expected > behavior?
See https://issues.apache.org/bugzilla/show_bug.cgi?id=47343 and https://issues.apache.org/bugzilla/show_bug.cgi?id=46924 and http://markmail.org/thread/bqxo3z26lpges7kc and http://tomcat.apache.org/tomcat-6.0-doc/config/host.html#Automatic_Application_Deployment (some detailed explanation is there; may be hard to find because it is in configuration docs) AFAIK, on an undeploy the context file is always deleted, because its presence means that the app is still deployed. If redeploy is implemented as undeploy + deploy, it would be hard to preserve that context file, especially if deploy fails. BTW, Tomcat 7 has different behaviour regarding context files: it does not copy them to conf/** by default. It is changed by "copyXML" attribute on a <Host>. > It seems that you wouldn't want external configuration files > removed on a redeployment. Of course I'm just testing out a new system and > in production I'm not sure I'd be just copying in a new war file and calling > that a redeployment... I'll change permissions on that file and see what > happens. Thanks for your insights. > > Jason > Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
