tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 52138] global web.xml servlet-mappings are not used when additional mappings are defined in app web.xml
Date Sun, 06 Nov 2011 21:29:43 GMT

James DeFelice <> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |

--- Comment #2 from James DeFelice <> 2011-11-06 21:29:43
UTC ---
Servlets defined in global web.xml are inherited by webapp web.xml.  New
servlets defined in web.xml do not eliminate servlets declared in global
web.xml, instead they are merged - this spares the app developer from needing
to declare the JspServlet, DefaultServlet, etc. in their webapp web.xml files
alongside their proprietary servlet declarations.

Mappings defined in global web.xml are also inherited, by default, in the
webapp. However, if new mappings are added in web.xml, then global web.xml
mappings are dropped. Web developers that want to add new mappings for servlets
declared in global web.xml are forced to re-declare the mappings in their
webapp web.xml because they are not automatically inherited.

Why would the design of servlet declaration inheritance be out of sync with the
design of servlet mapping inheritance?  Especially since servlet and servlet
mapping declarations have such a close relationship?

This behavior seems inconsistent at best.  I'd like to understand the rationale
behind this design decision, and how this does not constitute a design bug.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message