Dear Chuck,
>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.
Reading that I understand what you have pointed out and of course fully agree
to it :)
Greetings
Guid
On 8/22/18, 7:18 PM, Caldarale, Charles R wrote:
Not really a hierarchy, but just name your .war files (or directories)
appropriately:
foo#ham[.war]
foo#eggs[.war]
Look here for more info:
http://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Naming
Thanks. That answers my ques
> From: Jäkel, Guido [mailto:g.jae...@dnb.de]
> 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
ay, August 23, 2018 4:19 AM
>To: Tomcat Users List
>Subject: RE: Contexts: can there be a hierarchy?
>
>Not really a hierarchy, but just name your .war files (or directories)
>appropriately:
-
To u
> From: James H. H. Lampert [mailto:jam...@touchtonecorp.com]
> Subject: Contexts: can there be a hierarchy?
> Suppose we have a Tomcat 8 server
Let's hope that's Tomcat 8.5, since 8.0 has reached EOL.
> Is there a way to set up contexts in a hierarchy, such that requests for
> "https://xyz.ex
