On 17/12/2013 11:16, Jose María Zaragoza wrote: > 2013/12/17 André Warnier <a...@ice-sa.com>: >> Hi. >> Without having any idea really of the precise mechanism behind database >> connections, I can still imagine that with the possibility of pooled >> connections to said database(s), it may be difficult to detect such a change >> in the corresponding context.xml and apply them "on the fly". Even more so >> if such connections could be shared between different applications. > > > Thanks, but I didn't said that I neeed to apply changes "on the fly". > Indeed, I said "Restart the web application is not a problem" > > I only wan't to have to redeploy the web application to modify > META-INF/context.xml and apply changes.
How do you feel about a Tomcat upgrade? Automatic deployment has had a bit of an overhaul in Tomcat 8 and those changes have been back-ported to 7.0.x for the next release. The behaviour in a number of edge cases is now clearly defined: http://ci.apache.org/projects/tomcat/tomcat8/docs/config/automatic-deployment.html In your case, you'd want to deploy as a WAR with unpackWARs set to true. Then, any time you edit the META-INF/context.xml in the unpacked directory the web application will be redeployed using the new context.xml This might work with 6 but I can't remember (it is a long time since I looked at the 6.0.x automatic deployment code). Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
