> From: Jäkel, Guido [mailto:[email protected]] > Subject: RE: Contexts: can there be a hierarchy?
> why do you call it not really a hierachy? If you name the deployments e.g.
> ROOT.war
> foo.war
> foo#bar.war
> then the "expected" will happen: The longest context path will match to
the
> corresponding container:
> * all /foo/bar{,/.*} will be served by foo#bar.war,
> * all other /foo{,/.*} will be servered by foo.war
> * all other {,.*} will be served by ROOT.war
It's a hierarchy for the URLs, but not from a webapp location, construction,
or execution perspective - /foo/bar is completely independent of /foo, not
inside or a subset of it.
- 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.
smime.p7s
Description: S/MIME cryptographic signature
