Hello Chuck,
Actually, I'm getting a 400. I have read many pages (including the link
you've provided) and agree that the consensus is that the context tag
(in META-INF) should be empty if there at all. However, regardless of
how I populate the <Host> tag in server.xml, I always get a 400 (so now
I'm in trial and error mode).
I should point out that the whole set up works when I add a <Context>
tag within the <Host> tag (in server.xml) and set the docBase. I should
not need (nor do I want) to have a <Context> tag in server.xml.
Thanks,
Matthew
Caldarale, Charles R wrote:
From: Matthew [mailto:[EMAIL PROTECTED]
Subject: Re: Who do I have to pay (and how much) to...
I believe there is a way of specifying the context information in
context.xml that resides in the META-INF directory of the hosts .war
file.
That is the preferred mechanism. Read the doc:
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
Where the contents of the context.xml files are as follows...
<Context path="?????" docBase="?????"/>
You do not use either the path or the docBase attribute when the
<Context> element is located in the META-INF/context.xml file. These
are derived from the deployment name of the app. You usually don't need
a <Context> element (or context.xml file) at all.
Your 404 may be arrising because you're erroneously trying to specify
these attributes, or it may be something else entirely, such as not
having a welcome file in the webapp.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
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: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
