[jboss-dev] Annotation scanning in wars doesn't work anymore

Rémy Maucherat remy.maucherat at gmail.com
Thu Nov 26 11:54:44 EST 2009


On Thu, Nov 26, 2009 at 5:45 PM, Emanuel Muckenhuber
<emuckenh at redhat.com> wrote:
> Hmm we also need to make sure that you can use the AnnotationEnvironment
> (or the outstanding Papaki annotation scanning thingy) instead of the
> AnnotatedClassFilter in future. AFAIK the later one was much slower. It
> also means that the classpath is scanned twice for annotations (first
> from AE and then from the AnnotatedClassFilter) which should be avoided.
>
> I guess you cannot use the AnnotationEnvironment for now since you need
> scanning the reference to the web-fragment/jar?

Yes, scanning per JAR is needed, I did put it in the requirements wiki
for future annotation work.

Right now, it's either:
1) use the slow AnnotationMetaDataDeployer everywhere
2) use WarAnnotationMetaDataDeployer for web stuff and
OptAnnotationMetaDataDeployer elsewhere
Solution 2) is used.

For Carlo: You can update OptAnnotationMetaDataDeployer as you need,
web annotations processing is not done there. Your change looks ok to
me.

Rémy




More information about the jboss-development mailing list