"alesj" wrote : I'll change the order of DeploymentAliasMetaDataDeployer by
renaming it to AliasMetaDataDeployer.
| Not that it matters in state machine ;-), but I think it is less confusing.
| This way 2nd deployment will resolve the alias bean right away.
Bad choice, since that way the joined-beans.xml test case doesn't work.
In order to have AliasMDDeployer after BeanMDDeployer we need to run resolveContexts() on
the Controller, checking if some existing beans get resolved due to 'added'
context.
But I don't see the equivalent behavior on the removal of the alias.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062118#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...