[Bug 62945] JarScanFilter with tldSkip in context.xml still produce INFO msg. if one jar is scanned due to another reason
https://bz.apache.org/bugzilla/show_bug.cgi?id=62945 --- Comment #3 from Remy Maucherat --- (In reply to Andrei Costescu from comment #2) > It would be nice if the default config (that seems to be aware of > log4j-web*.jar already) would not - by default - assume that this jar has > also TLDs. That would require though that the global config needs to > allow/disallow jar scanning at a more granular level (so in this case > separate properties that apply only for TLD scanning). > > Could the default config be modified in that way? Current approach works but > I don't like the copy/paste needed to override jarsToScan with tldScan > (default jarsToScan could be changed I guess in future versions). Although > of course in the end the .war knows what is in it and can adjust these lists > to compensate for defaults. log4j-web isn't useful for TLDs, but contains other components which are scanned. Although it could be separate, both TLD and "other" scanning use the same default list, which means you can get the message for them. -- 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
[Bug 62945] JarScanFilter with tldSkip in context.xml still produce INFO msg. if one jar is scanned due to another reason
https://bz.apache.org/bugzilla/show_bug.cgi?id=62945 --- Comment #2 from Andrei Costescu --- Hmm, you are right. I posted a bug directly because it seemed at that time obvious that it was a bug. Next time I will post on the mailing list first. So I see that conf/catalina.properties does list the jar (with wildcard) that caused my problem: tomcat.util.scan.StandardJarScanFilter.jarsToScan=\ log4j-taglib*.jar,\ log4j-web*.jar,\ log4javascript*.jar,\ slf4j-taglib*.jar So now if I override this list by using in my META-INF/context.xml this: then indeed the warning goes away. It would be nice if the default config (that seems to be aware of log4j-web*.jar already) would not - by default - assume that this jar has also TLDs. That would require though that the global config needs to allow/disallow jar scanning at a more granular level (so in this case separate properties that apply only for TLD scanning). Could the default config be modified in that way? Current approach works but I don't like the copy/paste needed to override jarsToScan with tldScan (default jarsToScan could be changed I guess in future versions). Although of course in the end the .war knows what is in it and can adjust these lists to compensate for defaults. -- 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
[Bug 62945] JarScanFilter with tldSkip in context.xml still produce INFO msg. if one jar is scanned due to another reason
https://bz.apache.org/bugzilla/show_bug.cgi?id=62945 Remy Maucherat changed: What|Removed |Added Resolution|--- |INVALID OS||All Status|NEW |RESOLVED --- Comment #1 from Remy Maucherat --- In many cases you should investigate on the user list, especially since you sound a bit unsure. Here, although you looked at the jarsToSkip property, you didn't look at jarsToScan. -- 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
