tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject Re: Why deleting of context.xml is NOT optional ? (after deploying the app)
Date Fri, 06 May 2011 15:21:11 GMT

thank you for your answer.

Best regards,


> Od: "Christopher Schultz" <>
> Komu: Tomcat Users List <>
> Datum: 06.05.2011 16:05
> Předmět: Re: Why deleting of context.xml is NOT optional ? (after deploying the app)
>Hash: SHA1
>On 5/6/2011 8:29 AM, wrote:
>> hmm, "definitely" you are right that the files are deleted on "undeploy" not "deploy"
>> but don't you think it doesn't matter from the user's point of view ?
>Precision counts when describing bugs. Please be precise.
>Tomcat deletes an auto-deployed context.xml file when a WAR file is
>updated. It's quite clear in the documentation:
>See the fifth bullet point in the second section:
>* Updating a WAR file will trigger an undeploy of the application with
>the removal of any associated expanded directory, context file and work
>directory. Any current user sessions will not be persisted.
>If you don't want this to happen, don't update your WAR file. Instead,
>consider using the manager to STOP and START your webapp instead of
>triggering an automatic UNDEPLOY.
>> So you say that's definitely fixed for Tomcat 7, but still not fixed in Tomcat 6,
>> thank you for this hint, this will be the reason for me to migrate to 7.
>The behavior you are describing is by design, and thus cannot be changed
>within a particular version (6.0.x in this case) of Tomcat. Switching to
>another magor version gives the designers the freedom to make such
>breaking changes to the behavior of Tomcat.
>- -chris
>Version: GnuPG v1.4.10 (MingW32)
>Comment: Using GnuPG with Mozilla -
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message