"gregory.mostizky(a)gmail.com" wrote : I think it makes sense that the one you posted is the one causing the conflict. | Just from quick look at its source code, it seems that it applies additional filtering and scoping on top of GenericAnnotationDeployer which is consistent with what I saw when I disabled my custom deployer - I could get AnnotationEnviroment but some classes were missing (i.e. filtered out). | Ah, ic. Yes, we do some filtering chain, in order not to scan too much by default. But you can change that easily. "gregory.mostizky(a)gmail.com" wrote : | So the root of the problem seems to be that it is possible to use both of them and each one will try to overwrite AnnotationEnviroment attachment with slightly different data resulting in unpredictable behavior. Since both attachments are valid the fix IMO should be just assigning unique "attachment ids" to each one instead of both sharing AnnotationEnviroment.class I still think we should force usage of a single AE. As encouraging multiple AE is not the way to go, performance wise in the first place. I'll need to change this filtering anyway, as I should do scanning no matter if JBossMD says it's complete. e.g. I should scan @Entity anyway View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228656#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...