To: Tomcat Users List
Subject: Re: Context.xml not updating dataSource
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
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
You could always silo offending applications like that into their own
containers - give them their own space and let them not affect the rest of your
infrastructure. How you interact with that application/service may dictate
your ability to do that cleanly, but those are larger architectural
This also worked correctly (as documented) for me with 6.0.20 - with the build
of extras and log4j off the SVN trunk (patches for certain property handling
due out in 1.2.16)
--
Mike
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Friday, June 26, 2009 4:01 PM
To:
Hi,
Trying to understand behavior of TC (6.0.x) deployment process of webapps
with the following Host definition (server.xml):
Host name=localhost appBase=webapps
unpackWARs=true autoDeploy=true deployXML=false
xmlValidation=false xmlNamespaceAware=false
In short, we want to
