We're talking about Tomcat 5.5, not 5.0, and about a specific deployment
But you're right that the 5.5 docs are not updated to correctly reflect
this new logic. We had a debate and a couple of implementations as to
when to take and when to ignore the path and docBase attributes, i.e.
when they are optional and when required. We've yet to update the
Context docs, so they are a bit misleading for 5.5 now. A path is of
course still required, but the user doesn't have to specify it, as
Tomcat will now deduce it in some cases.
> says, "Each such Context MUST have a unique context path, which is
> by the path attribute" which implies that we must include the path
> in a <Context>, wherever it is configured. Perhaps the docs do need a
> slight fix to reflect what you say below?
> > Since the path attribute is redundant information, it is ignored in
> > context.xml files. Same for docBase in many cases.
> > Please do not open a bug report about this, or propose switching
> > to the old behavior.
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.