The changes have changed. The new changes are: 1. unpackWARs now applies to external WARs as well as WARs located in the Host's appBase.
2. If a WAR is modified (located in the Host's appBase or externally) and there is a context.xml file present in the Host's appBase (which there must be for external WARs) then Tomcat now reloads the web application rather than redeploys it as the Context configuration (defined in the context.xml file in the Host's configBase) hasn't changed. I currently believe that all of the above changes would be safe to back-port to Tomcat 7. The expected behaviour is documented at [1]. The test cases are complete for: - clean deployment - resource deletion - resource modification I still need to implement the tests for resource addition. Now is a good time to start trying to break the automatic deployment code. Any testing, review of the changes, comments on the defined behaviour etc. are welcome. Mark [1] http://people.apache.org/~markt/dev/auto-deployment-proposed.txt --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
