On 09/04/2015 13:25, Pravallika Peddi wrote: > Hi Mark, > > > > I can add the Boolean variable at ContextConfig class level so that all > pluggability scans can access it and set the value accordingly.
That is too high. It needs to be per JAR. > Almost all web-inf/lib/class scans are internally calling > “processAnnotationsStream()” method of ContextConfig.java. So in this > method I can change the Boolean variable to true if annotations are found. Almost? That isn't really good enough. This has to be comprehensive to be useful. > Here the problem is: In case if a JAR is unnecessarily processed we can > ask user to add that jAR under “JarsToSkip” property. But in case if a > class file is scanned unnecessarily, we cannot ask user to add it under > “JARsToSkip” property. > > So I felt there is no point in handling for class scans. I agree for classes under WEB-INF/classes. For classes in a JAR then if all the classes are scanned unnecessarily then the JAR is a candidate for being skipped. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
