On Thu, 06 Aug 2009 23:52:24 +0200, arjan.tijms <arjan.ti...@m4n.nl> wrote: >>Search the archives. This been covered repeatedly. >>Mark
I did found this posting: http://mail-archives.apache.org/mod_mbox/tomcat-users/200906.mbox/%3c4a3f56c9.8050...@apache.org%3e You explain here the copying of the context.xml that's within a .war archive and a few posts later the reasons for doing so. Although maybe not explicitly documented, it seems Tomcat has been doing this at least for a while for .war archives. However, in my case I'm statically deploying an *exploded* web application. I just tested whether earlier Tomcat versions copied context.xml (I used Tomcat 6.0.14, 6.0.16 and 6.0.18) and none of these did the copying for static exploded deployments. Can you confirm that copying for exploded deployments is a new and intended behavior for Tomcat 6.0.20? If this is indeed intended behavior, then what is the rationale for it? Unlike for .war deployments, I can just edit the embedded context.xml in an exploded deployment directly so the "unpack, edit, pack" problems aren't an issue here. Also, for development I'm running into issues too with the new behavior. If I edit the context.xml file in Eclipse and save it, then Tomcat 6.0.18 would pick up the changes. Since my IDE has no knowledge about the file in conf/Catalina the result is that changes don't seem to be picked up. Manually deleting the file in conf/Catalina on the command line outside my IDE is of course not difficult but tedious nevertheless. Also, in this post http://mail-archives.apache.org/mod_mbox/tomcat-users/200906.mbox/%3c4a3f70cb.8050...@apache.org%3e you say: >If you want to remove the old configuration, undeploy the app first which will remove the old configuration file. But what counts as an "undeploy" for a static deployment? If I just delete my statically deployed application from the webapps directory and restart Tomcat, then the files in conf/Catalina are still there. Instead of removing the configuration files, Tomcat gives the error that it can't find the matching webapp anymore. Does this undeploy that should remove the configuration file only works when undeploying via the manager app? Arjan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
