https://issues.apache.org/bugzilla/show_bug.cgi?id=52607
--- Comment #2 from Mark Thomas <ma...@apache.org> 2012-02-08 20:14:22 UTC --- I've done some svn archaeology and r302820 is most enlightening. Originally, only java.ext.dirs was supported. r302820 was the start of exposing the common and shared class loaders to the validation mechanism. I don't see any intention of providing a separate directory. Given that the spec says that extensions have to be loaded by the shared class loader, I also don't see any benefit in having an additional system property. It is simpler for users just to modify the class path for the shared (or common - it meets the requirements of the spec too) class loader. However, the problem remains that the ExtensionValidator will not find the JARs in the shared or common class loaders. That certainly needs to be fixed. I guess that is the long way of saying I think 2 is the way to go. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
