Also, let me explain a little better.
I am reading this section in the Docs: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/host.html#Automatic%20Application%20Deployment
And it indicates I can autoDeploy by creating a file *.xml with a <Context> tag inside. This will act as if that context was entered in my server.xml. This enables me to control where my WAR will be deployed via a file external to server.xml. This is exactly what I want.
The second autoDeploy takes each *.war file and deploys it to a webapp named the same as the war file. For example, my SoiledDove.war gets deployed to a /SoiledDove webapp.
Because my context XML file deploys to path="" (the ROOT context in other words), AND my SoiledDove.war file is in the webapps directory... I am getting double auto-deployment.
How can I control which autoDeployment methods are enabled for a particular WAR?
Thanks, Aaron
Aaron Longwell wrote:
I'm deploying a WAR file to the root context (path=""). I've created the appropriate context XML file in the webapps dir and pointed it to a WAR (which I do NOT want to be expanded). It's working great... except for one thing:
Tomcat is deleting the context XML file.... so that when I stop and restart the server, my WAR file is re-deployed at /WARFileName instead of /
Why does tomcat delete this XML file for my webapp but not for Admin or Manager webapps? Am I doing this incorrectly?
Thanks, Aaron
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]