https://issues.apache.org/bugzilla/show_bug.cgi?id=53395
--- Comment #2 from Mike Tillberg <mike.tillb...@yahoo.com> --- It looks like auto deploy is implemented as a undeploy followed by deploy: Jun 11, 2012 10:15:26 AM org.apache.catalina.startup.HostConfig checkResources INFO: Undeploying context [/webapp] Jun 11, 2012 10:15:26 AM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive webapp.war The broken context then causes: Jun 11, 2012 10:15:26 AM org.apache.catalina.startup.HostConfig deployWAR SEVERE: Error deploying web application archive webapp.war So, if the deployment failed, why is the war considered "deployed" for the purposes of retaining the context.xml file? Wouldn't it be better for the failed context.xml to be removed if it can't be parsed? Or at least (if I'm reading the code correctly) setup the deployedApp.redeployResources/addWatchedResources in HostConfig so that tomcat doesn't lose track of the app? After a failed deploy, both modifying the war file or removing the war file do not trigger auto deploy or undeployment. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
