On Monday 20 July 2009 17:08:15 Mike Frohme wrote: > > > >> Edit the copy of the context.xml file and all will work as you > > > >> expect. > > > > > > 1. In production, the operations folks don't have to unpack the app, > > > edit the context file and re-pack the app to edit the configuration. > > > > > > 2. When a new version of the app is installed, the environment specific > > > configuration isn't lost. > > > > > > If you want to remove the old configuration, undeploy the app first > > > which will remove the old configuration file. > > > > A an aside, wouldn't it be nice if it were configurable whether tomcat > > copies the context.xml to $CATALINA_BASE/conf? Then administrators could > > decide to never have local configuration and always rely on the config > > within the war? > Sorry for the late reply, Rainer. > > There is, in principle. Set deployXML to false in the Host declaration in > your server.xml and it will do exactly what you want. On the flip side, > tomcat will remove the configuration when the app is undeployed, so you > need a little care in your deployment process.
Thanks for the response. Actually, doesn't this do the exact oposite of what I want? What I want (as option): "I know that developer/packager did it right and I never want to have local configuration. Always use the context.xml within the currently deployed application, updated every time I redeploy the app." deployXML=false seems to do: "Never trust the developer, don't even copy their context configuration to local configuration if there is no local one yet. Only use a configuration I manually put on the server". Could anyone please comment whether I understand that right? > Mike Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
