Hi, I just noticed a surprising behavior change between Tomcat 5.0 and Tomcat 6.0.18 regarding auto-undeployment of war files. I use both versions in default configuration, which means autoDeploy and unpackWARs are both true.
(I don't think this matters much, but I tried this with Mac OS X and Java 5 as well as Linux and Java 6). In Tomcat 5.0, I copy the war file to the webapps directory, it is unpacked and deployed. Then I can delete the war file, and the web application runs and will be deployed on next start from the unpacked directory. In Tomcat 6.0 deployment works the same, but when I delete the war file, the application is undeployed and the expanded directory is deleted. Is this change documented somewhere, and is there a way to get the old behavior with tomcat 6.0? Also I think that in Tomcat 5, it was *necessary* to delete the war file to be able to edit the web.xml ofthe deployed application, otherwise it was overwritten from the war file at least at the next server start. What will Tomcat 6 do on startup in this case (a .war file *and* an expanded directory of the same webapp exist, with a newer web.xml in the expanded directory? My question regards development, so there is no need to convince me that autodeployment should not be used in production :-) Regards Rainer Frey --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
