tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Kjome <>
Subject Re: deploy in 4.1.24
Date Wed, 28 May 2003 21:45:01 GMT

All I can say is that you must be mistaken.  I just performed a <deploy> 
with two different apps.  In both cases, the .war files ended up in 
work/Standalone/localhost/manager and the WEB-INF directory from those .war 
files were also extracted to work/Standalone/localhost/[webapp  name].

In no case was anything placed in the webapps directory.

This test was performed on Tomcat-4.1.24 and the latest CVS build of Tomcat-5.


At 11:48 AM 5/28/2003 -0500, you wrote:
>I'm upgrading from 4.1.12-LE to 4.1.24-LE, and have found what appears to 
>be a change in behavior from the <deploy> and <undeploy> tasks in 
>In 4.1.12, the webapp appeared to be deployed to 
>TOMCAT_HOME/work/standalone/localhost/<webapp>.  It was not placed in the 
>TOMCAT_HOME/webapps folder.  This appeared to work fine, though, as the 
>app was properly deployed, it worked, it was persisted, etc. etc. 
>etc.  The task could then be <undeploy>'d.
>In 4.1.24, war file is placed in the TOMCAT_HOME/webapps folder, and the 
>app is deployed from there.  This also works fine for deployment (the app 
>works, persisted, etc. etc. etc.).  BUT -- the <undeploy> fails.  I can 
>use the <remove> task to remove the app, though.
>Is this an intentional change in behavior?  If so, is there any case where 
>the <undeploy> task should (could?) be used?
>Paul Christmann
>Prior Artisans, LLC
>To unsubscribe, e-mail:
>For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message