Bug 53714 - misleading log output when jarsToSkip cointains web-fragments
Summary: misleading log output when jarsToSkip cointains web-fragments
Alias: None
Product: Tomcat 7
Classification: Unclassified
Component: Jasper (show other bugs)
Version: 7.0.26
Hardware: PC Linux
: P2 minor (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2012-08-14 09:13 UTC by Volker Krebs
Modified: 2012-08-24 20:23 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Volker Krebs 2012-08-14 09:13:38 UTC
I have a jar which contains a web-fragment and no TLDs. When starting the server I get the Message:

org.apache.jasper.compiler.TldLocationsCache tldScanJar
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

so far so good.

When adding it to the tomcat.util.scan.DefaultJarScanner.jarsToSkip property the web-fragment won't be scanned either.

The log message should only be printed when no TLDs and web-fragments could be found in the jar.
Comment 1 Mark Thomas 2012-08-24 20:23:00 UTC
Fixed in trunk and 7.0.x and will be included in 7.0.30 onwards.

Note the fix was implemented using additional system properties. Determining if a JAR had contributed to a Servlet 3.0 pluggability feature and then passing that info the the TLD scanner would have been a much more invasive patch.