My problem is that a paying customer has been waiting for an AOP 2.0 alpha for ages and the new tight integration with the container project is holding things up. I will look at making including the container specific stuff in AOP a configuration option so that the alpha release can work in JBoss 4.0 as-is (with no need to update the jboss-beans.deployer) and also work in JBoss 5 with the MC. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972616#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...