Mark Thomas wrote:
Ken Bowen wrote:
The Host spec from server.xml:
<Host appBase="webapps" name="myaddress.com" unpackWARs="true"
autoDeploy="true">
<Context path="/manager"
docBase="/opt/tomcat5/server/webapps/manager" privileged="true" debug="0"/>
<Context path="/admin" docBase="/opt/tomcat5/server/webapps/admin"
privileged="true" debug="0"/>
</Host>
It looks like you have a third-party packaged version of Tomcat. It
might not be the cause but you might be better off with a standard
version downloaded from Apache or one of its mirriors.
Indeed. I don't have so much control over the system on the ISP.
However, on my own box (Linux),
I installed a completely vanilla unzipped download from Apache.
Everything worked exactly as
it is supposed to: Rename myapp.war to ROOT.war, drop ROOT.war in
webapps, and it is expanded
and the app is running as the default context.
Now to figure out how to coax the ISP into doing the right thing.... :-(
Thanks,
Ken Bowen
The META-INF/context.xml for myapp:
<Context path="" debug="5" reloadable="true" crossContext="true">
Remove the path element - it isn't necessary.
When cleaning things up - don't forget about $CATALINA_HOME/conf
You might have an old context file in there confusing things.
Mark
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
