I've tried that, it doesn't work. Updating a WAR file will trigger an undeploy and consequent removal of the context descriptor in a running Tomcat if the Host autoDeploy attribute is true.
If autoDeploy is false, redeploy without updating the context.xml can occur using the manager. p On 12 April 2010 10:34, Pid * <p...@pidster.com> wrote: > If you're uploading directly to the webapps directory, try uploading the > file renamed to "yourapp.warTMP" and renaming it in place when the upload is > complete. > > Please let us know if this works/does not work. > > > p > > On 12 April 2010 09:18, Pid * <p...@pidster.com> wrote: > >> Which version of Tomcat are you using? >> >> >> p >> >> >> On 12 April 2010 01:35, Sam Stephens <samspad...@gmail.com> wrote: >> >>> Hi all. >>> >>> The tomcat documentation says the following: >>> If the web application is packaged as a WAR then /META-INF/context.xml >>> will be copied to $CATALINA_BASE/conf/[enginename]/[hostname]/ and >>> renamed to match the application's context path. Once this file >>> exists, it will not be replaced if a new WAR with a newer >>> /META-INF/context.xml is placed in the host's appBase. >>> >>> However, each time I upload a new WAR the existing context.xml gets >>> deleted and replaced with the one inside the WAR file (which is just a >>> default). So I lose all my configuration details. >>> >>> I have googled and it seems this is a common problem. Any help ? >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >>> >> >> >> -- >> >> -- >> pidster.com >> > > > > -- > > -- > pidster.com > -- -- pidster.com
