Re: Always loading default web.xml ?

[Craig R. McClanahan]

On Tue, 12 Jun 2001, Remy Maucherat wrote:

> Hi,
> 
> I have the impression that we're always loading the default web.xml, even if
> the webapp already contains one, and add to the mappings which are defined
> there.
> 

Yep.  Tomcat loads the default mappings from this file, then it loads your
own mappings (which override anything set in the defaults).

> I think it's ok when no mapping are defined, or no mapping is defined on the
> root node, but it's not as soon as a mapping is defined on either / or /*
> (which would indicate that the user wants to have all requests in the webapp
> handled by a particular servlet).
> 
> Here, I'd like to have one servlet handle everything, including *.jsp, while
> leaving the default web.xml intact (so that Jasper is still active in other
> contexts) ;-)
> 

If you map to "/*" in your own web.xml, it overrides any "*.jsp" mappings
in the defaults (because of the priority ordering defined in the servlet
spec).  What is it that you feel you cannot do?

> If the feature isn't present somewhere already (and I missed it), I think we
> should add it.
> 
> Remy
> 
> 

Craig