tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Caldarale, Charles R" <>
Subject RE: Manager deploy uploaded war - doesn't use the /WEB-INF/context.xml
Date Wed, 15 Nov 2006 22:44:38 GMT
> From: Tim Alberts [] 
> Subject: Re: Manager deploy uploaded war - doesn't use the 
> /WEB-INF/context.xml
> The server seems to be doing this?  I have a file in conf/ [engine] / 
> [host] named with the # symbol 'path#to#myapp#app.xml and it 
> contains the context element with the correct path 'path/to/myapp'.

There should be no path attribute in a <Context> element unless the
element is within server.xml.  The one you're referring to in
conf/[engine]/[host] is just a copy of what's in META-INF/context.xml,
renamed to the path of the app during deployment.  I haven't yet chased
down exactly when Tomcat copies the context.xml from META-INF into

> I also have the path#to#myapp#app.war in the webapps directory
> so it uploaded, but it is not unpacking the war into ANY location.

This has nothing to do with unpacking WARs.

For the moment, you may have to keep your app outside of Tomcat's
webapps directory, and explicitly place your <Context> element - with
docBase - into conf/[engine]/[host]/path#to#myapp.xml (not
path#to#mayapp#app.xml).  Tomcat 5.5.20 does not seem to like .war names
with #-symbols in them.

 - Chuck

MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message