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 manually manage conf/[engine]/[host]/appname.xml files for
each webapp. Almost everything works exactly as expected. The only odd
behavior is that on an application re-deploy, the (manually managed)
conf/[engine]/[host]/appname.xml is removed as part of the undeploy process.
The docs seem to support this, but it seems wrong somehow.
Yes, I know the docs also say you should "probably turn off auto-deploy if you
explicitly manage context" - we're working on our process for that.
In short, this perceived lack of symmetry in the behavior prompted me to ask
the question. ...
When deployXML is false ... if you don't parse and update context on deploy,
why would you do it on undeploy?
As additional info, no <Context> blocks are defined in server.xml, and apps are
deployed as WAR files. Yes, they contain a META-INF/context.xml - used locally
in development, but not in the deployed environment.
Thanks for any insight/feedback you might have.
--
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
