tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 54261] web-fragment.xml handling in container JARs
Date Sun, 09 Dec 2012 11:25:13 GMT

--- Comment #2 from Mark Thomas <> ---
The relevant section is:
If a framework wants its META-INF/web-fragment.xml honored in such a way that
it augments a web application's web.xml, the framework must be bundled within
the web application's WEB-INF/lib directory. In order for any other types of
resources (e.g., class files) of the framework to be made available to a web
application, it is sufficient for the framework to be present anywhere in the
classloader delegation chain of the web application. In other words, only JAR
files bundled in a web application's WEB-INF/lib directory, but not those
higher up in the class loading delegation chain, need to be scanned for

The wording isn't as clear as it could be but the Servlet 3.0 EG lead has
confirmed the intended behaviour is as per my description. And yes, they should
still be scanned for TLDs.

I haven't tried to understand the reasoning behind this decision. My head hurts
enough already from just trying to nail down what the intended behaviour is
meant to be. I have thought through the implications for WebSocket and there
isn't anything I am worried about at this point.

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