Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of joe.k@centrum.cz designates
 90.183.38.155 as permitted sender)
To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: Why deleting of context.xml is NOT optional ? (after deploying
 the app)
Date: Fri, 06 May 2011 17:21:11 +0200
From: <joe.k@centrum.cz>
References: <20110506100846.4C6D073E@centrum.cz> <4DC3B16E.1000405@apache.org>
 <20110506142940.90D11D78@centrum.cz>
 <4DC40000.1000101@christopherschultz.net>
In-Reply-To: <4DC40000.1000101@christopherschultz.net>
MIME-Version: 1.0
Message-Id: <20110506172111.FBD56AD2@centrum.cz>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit


Chris,
thank you for your answer.

Best regards,

Joe


______________________________________________________________
> Od: "Christopher Schultz" <chris@christopherschultz.net>
> Komu: Tomcat Users List <users@tomcat.apache.org>
> Datum: 06.05.2011 16:05
> Předmět: Re: Why deleting of context.xml is NOT optional ? (after deploying the app)
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Joe,
>
>On 5/6/2011 8:29 AM, joe.k@centrum.cz 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:
>
>http://tomcat.apache.org/tomcat-6.0-doc/config/host.html#Automatic%20Application%20Deployment
>
>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
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.10 (MingW32)
>Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
>iEYEARECAAYFAk3EAAAACgkQ9CaO5/Lv0PAaHgCfSJgxCd1GshlVE0pkiXXrCJOG
>9H4AoKx5WhQvSP6eFB3J2VhJT04MSTxS
>=qaQr
>-----END PGP SIGNATURE-----
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org