[jboss-dev] annotation scanning

Ales Justin ales.justin at gmail.com
Wed Oct 28 13:16:13 EDT 2009


> Nothing changed in metadata. However, due to the Servlet spec, I had
> to switch back to using the old annotation deployer rather than
> OptAnnotationMetaDataDeployer to process the stuff that is in WARs. 

Yeah, that's what I meant.

But like I said, the problem is in how Metadata uses this info.
Instead of just pull model, we have a push-pull-push model. :-)

> could become a problem for WARs with tons of JARs.

This is something you cannot do much faster.
The fact is that you have to scan everything the users expects to be 
scanned,
and mostly this is everything, small or huge, doesn't matter.

The things that (should/will) help here are:
* scan only once, everybody else just uses this info,
   no additional scanning; which is not the case atm
* restrict what should be scanned; jboss-scanning.xml
* use exact class import/export info; osgi/jboss-classloading.xml
* pre-indexed scanning; META-INF/anns.ser

> Right, the grouping per location is the extra feature that is needed
> for Servlet 3.0.

I/We will add this once we decide what to do.
Which current impl we actually use and maintain. ;-)



More information about the jboss-development mailing list