This is issue d) in Konstantin's comments in TOMCAT-NEXT.txt Konstantin is right to point out the inefficiencies in JarScanner. There is no need to scan WEB-INF/lib and WEB-INF/classes as the class path from the WebappClassLoader already includes them.
However, I think this can be considered separately from the Resources implementation. My suggestion is to open a BZ enhancement request for this. My one comment is that we'll need to be careful to retain the current functionality of having the option to scan just WEB-INF or the entire class path. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
