Copied from http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169019#... "kabir.khan(a)jboss.com" wrote : "adrian(a)jboss.org" wrote : "kabir.khan(a)jboss.com" wrote : . | | | Another problem is that for scoped deployments I am changing the beans name to something unique and adding an alias annotation containing the bean name. This breaks with the new code in BeanMetaDataDeployer. I will post more on this once I have some more information about what exactly is going on... | | | | Why? | | | | You'll break all sorts of assumptions related to deployment components | | the metadata scopes, and reporting incomplete deployments if you do that wrong. | | | | It seems to me that you need to take a step backwards to the original problem | | and explain what you are really trying to solve, rather than try to figure out | | what has broken because you are hacking at things you shouldn't. :-) | | I spoke to Ales about this, it is (was) solving the problem mentioned here: | http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154037#... | Basically in a scoped deployment I deploy the aop beans with a new unique name, and use an annotation to create the alias, and an annotation to deploy the bean into a scoped controller. | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169023#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...