"kabir.khan(a)jboss.com" wrote : | Is this a bug, or have I completely misunderstood? | Misunderstood. :-) I really don't see exactly what you're trying to do, so I'll try to guess as I don't understand how scoped aspect domains work. ;-) Probably this is not an issue with scoped beans, since we've gone over that - proper @annotation + PreInstallAction do all the tricks. Or is it, since I see you've got something called scopedManager: | unit.getMutableMetaData().addMetaData(scopedManager, AspectManager.class); | Perhaps what you're missing here, is what I've added to scoped kernels impl - the @Search notion. Meaning you can localize your loookup - in this case just the same scope, not doing any parent lookup. Hence dependency doesn't depend on the order global and scoped aspect manager are deployed. But this is currently only annotation based, no xml. As for DeploymentUnit and its MetaData, I don't think this is currently used. But that should be how we eventually do scoped kernels - initial control/creation from the deployment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168626#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...