"adrian(a)jboss.org" wrote : | If you really want to exclude the AOPDependencyBuilder processing from a bean then | you should really use one of AOP's existing mechanisms like exclude "org.jboss.ejb3.*" | from having aspects applied to it (that can be configured on the AspectManager). | That's the hack that i tried when i first saw this behaviour :) And that's what showed me an improvement in the deployment timing. "adrian(a)jboss.org" wrote : | Otherwise you could just configure the dependency directly on the bean. | That's what we currently do for EJB3 containers. "adrian(a)jboss.org" wrote : | You'd be better off speaking to Kabir about how to optimise/avoid the AOP checking | for what you want than getting Ales to hack things into the MC that are fundamentally wrong. Sure, i don't mind trying out a different approach - whichever is the correct one :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230492#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...