tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Pepper" <>
Subject Re: Problem with JNDI environment entry resources
Date Wed, 03 Sep 2008 14:30:51 GMT
> I'll have to check the docs again.  However, docBase is only legal when the webapp is
stored outside of the <Host>
> appBase directory.  Otherwise, you risk ending up with double deployment.

I don't see docBase described that way in the docs - at this moment
I'm referring to Besides,
I don't see any other documented way of associating each application
with its associated <Context/> element within server.xml.

>> unless I named the application ROOT, which is less than ideal
> That is the defined mechanism for specifying the default webapp in current Tomcat levels.

That's one mechanism for specifying the ROOT application. Referring to, when
using individual context files under
    "The default web application may be defined by using a file called
The filename less the .xml provides the context path (/ in the case of
ROOT) and the <Context/> element's docBase points to the ROOT
application. This is all in accordance with the current 6.0 docs from
my reading of them.

I'd like to pull this out into a thread of its own on this mailing
list. Maybe we can take this discussion there. This particular problem
is of importance to me, and it would seem also to others judging by
the comments left on the bug report that I referenced in my previous

> Placing <Context> elements in server.xml is really only there for compatibility
with older versions of Tomcat.  Personally, I'd like to see it made illegal, which would put
an end to many potential configuration errors.

Then you'd be taking away the only mechanism (that I can see) for
pointing to an application as ROOT, without the inelegant renaming of
applications as ROOT.


To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message