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: The longest context path will match
On Thu, Aug 23, 2018, 2:06 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Bab,
>
> On 8/22/18 9:49 AM, Bab Alemzadeh wrote:
> > I am using Windows Server 2008/2012, datacenter edition. We have
> > installed: KB4338815.
> >
> >
Dear Chales (and James)
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 fo
On 22/08/18 19:48, Terence M. Bandoian wrote:
> Back on topic, do JSPs have to be registered with the container using
> servlet mappings in web.xml or some other mechanism in order to serve as
> targets of forwards by servlets? Further, does doing so make those JSPs
> accessible via external re
