[jboss-dev] Improving scanning performance

[Brian Stansberry]

Chris Bredesen wrote:
> Anil Saldhana wrote:
>> Bill Burke wrote:
>>> I suggested this a year or two ago:
>>>
>>> * You should have a AnnotationScanner deployer that scans jars for 
>>> annotations and puts an annotation database somewhere in memory that 
>>> other deployers can reference.  (This might already exist, I don't 
>>> know).
>>>
>>> * If a file META-INF/no.scan exists in a jar, then don't scan the 
>>> file.  This allows libraries to exclude themselves from scanning.
>> This is good.
>>> * If a file META-INF/scan.only exists it will contain a newline 
>>> delimited list of class names to scan.  Only scan those class names.
>> Why not just scan the jar with the presence of the file?  It will 
>> become cumbersome to list all the class names if they are many classes 
>> to be scanned in a jar??
> 

My interpretation of this is the absence of no.scan and scan.only means 
scan the entire jar. Which is the default so end users don't have to 
understand this stuff.

> Or support listing of *packages* and not just class names...

+1

> 
> -CB
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development


-- 
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry at redhat.com