Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-ID: <4021D87C.9090401@citysearch.com>
Date: Wed, 04 Feb 2004 21:45:32 -0800
From: Josh Rehman <jrehman@citysearch.com>
Organization: Citysearch - Make the most of your city
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: Tomcat Loads Deleted Context?
References: <001101c3eb5c$3b2c8d80$7202a8c0@stbedm.silvacom.com>
 <Pine.GSO.4.58.0402042250470.20083@shalom.cso.uiuc.edu>
In-Reply-To: <Pine.GSO.4.58.0402042250470.20083@shalom.cso.uiuc.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Amen to that brother. I wasted a lot of time having an old context load 
up on me with TC5 when I had removed it from server.xml.

Very, very bad idea tomcat developers!

Note that they *can't* delete that directory because you might have 
modified something by hand, and presumably that would be even worse. (Of 
course, you could check to see if anything had changed before deleting, 
this safer deletion is possible.)

Bottom line is that any piece of server software should have 
"reversable" behavior - if I make a change to a config file, and change 
it back, then the server should act the same way before the change was 
made at all. Tomcat doesn't do this, and that's very bad.

Now, if I am wrong about this, please correct me. I'm all ears!

Milt Epstein wrote:

I amend what I said before .  And I agree with you -- it should be
Tomcat's responsibility to delete the context configuration file it is
creating.


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