Does this apply only to scanning for fragments?

Or does it handle discovery of which jars do / don't need to be included due to 
@HandlesType?

What I'd really like to see is:
1. Run without a JarScanFilter, but with verbose logging
2. Receive the inputs for an optimal JarScanFilter configuration from that 
logging
3. Apply the optimal JarScanFilter configuration

Easy, peasy -- ideally covering both tldScan and pluggabilityScan at once.

-----Original Message-----
From: Hemanta Pathak <[email protected]> 
Sent: Thursday, June 4, 2026 7:57 AM
To: Tomcat Users List <[email protected]>
Cc: Holle, Jess <[email protected]>
Subject: RE: Logging of which jars did or didn't need scanning?

[You don't often get email from [email protected]. Learn why this is 
important at https://aka.ms/LearnAboutSenderIdentification ]

Enabling debug logging on org.apache.tomcat.util.scan gives the JAR list for 
your classpath.

The output would look like this:
05:06:51.234 DEBUG o.a.t.u.s.StandardJarScanner - Not including JAR 
[hibernate-core-5.6.x.jar] as it does not contain a web fragment

Regards,
Hemanta

-----Original Message-----
From: Holle, Jess via users <[email protected]>
Sent: Thursday, June 4, 2026 5:44 PM
To: [email protected]
Cc: Holle, Jess <[email protected]>
Subject: Logging of which jars did or didn't need scanning?

It would appear there's no definitive logging in Tomcat of which jars were 
found to need or not need scanning for purposes of an optimal JarScanFilter 
configuration.

Could this be added? Either a "yes, I found stuff in this jar that justified it 
being scanned" or "no, I found nothing in this jar to justify it being scanned" 
logging would be really helpful IMHO.

I find myself asking AI to try to discern such for larger library sets - or 
adding my own possibly errant attempts at such logging to Tomcat code.

--
Jess Holle

HealthEdge Software, Inc. is the owner of the information contained in this 
communication. The content of this communication is considered company 
confidential and may contain privileged information that is protected under 
various federal and state statutes. Disclosure of privileged information 
without the express written consent of an authorized legal agent of HealthEdge 
is strictly prohibited. Any unauthorized distribution or use of this 
communication, in part or whole, may constitute a criminal act. HealthEdge 
retains the right to pursue criminal and civil remedies in the event of any 
unauthorized disclosure.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to