You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2016/08/11 21:37:22 UTC
[Bug 59862] Allow Nested Jar Scanning to be Filtered with System
Property
https://bz.apache.org/bugzilla/show_bug.cgi?id=59862
--- Comment #6 from Mark Thomas <ma...@apache.org> ---
It was me that voiced concerns over this that led to the original commits being
reverted. I've now found the time to come back to this.
As far as the Servlet spec is concerned, JARs are located in WEB-INF/lib and
those JARs are not checked to see if they contain nested JARs.
However, the container is free to provide any mechanism it sees fit to augment
the web application's class-path. Tomcat does this in a variety of ways but
many of them boil down to providing a URL to a JAR to add to the class path.
That URL can point to a JAR file within another JAR if you take advantage of
the JarWarResourceSet (the outer JAR is treated as a WAR).
Having had a chance to work through the implications of the proposed patch I'm
happy that there are no issues. I'll get it re-applied.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org