DO NOT REPLY [Bug 4829] - Automatic deployment of war files does not work properly

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4829>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4829

Automatic deployment of war files does not work properly





------- Additional Comments From tim.cooke@chevin.com  2002-07-15 13:56 -------
Dear Remy

You have my full sympathy about this problem, but there is a lot of confusion 
occurring.

You're being perfectly reasonable both in pointing out that this isn't a bug at 
all, but the designed behavior, and in suggesting that bug reporters instead 
submit a patch to change the behavior.

The problem is that many people who are experiencing this bug, and this applies 
to me, are not technically adept enough to propose such a change - is there any 
chance that you could revisit the stated design and , or would this then 
contravene a specification?

What I believe people want or need is to be able to start Tomcat *with* a 
context (e.g. "MyApp") defined in server.xml, and with a "MyApp.war" file in 
place, but *without* the exploded "MyApp" webapp directory; in this scenario it 
would be most excellent if Tomcat unpacked the WAR before alternatively 
discovering the absence of the declared context.

What are your thoughts on this suggestion?

TIA

Kind regards
Tim Cooke
P.S. At present I run Tomcat 4.0.1.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>