Yes, I think AOPConstructorJoinPoint without the AOPDependencyBuilder is pointless, and vice versa. It would cause problems if the aspects actually have dependencies | <aop:aspect xmlns:aop="urn:jboss:aop-beans:1.0" | name="TxAdvice" | class="org.acme.aspects.TxAspect" | <property name="txManager"><inject bean="TxManager"/></property> | </aop:aspect> | <aop:bind xmlns:aop="urn:jboss:aop-beans:1.0" | pointcut="execution(* *->@org.acme.Tx(..))">; | <advice aspect="TxAdvice" name="invoke"/> | </aop:bind> | but not really of they don't | <aop:aspect xmlns:aop="urn:jboss:aop-beans:1.0" | name="Blah" | class="org.acme.aspects.Blah" | </aop:aspect> | <aop:bind xmlns:aop="urn:jboss:aop-beans:1.0" | pointcut="execution(* *->@org.acme.Blah(..))">; | <advice aspect="Blah" name="invoke"/> | </aop:bind> | But if you are sure you don't want aop for a set of beans, then both should be turned off View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230478#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...