"alesj" wrote : "adrian(a)jboss.org" wrote : | | I guess this is because it doesn't look like DefaultScopeBuilder in the deployers knows | | anything about classes when creating component scopes? | | It just adds the INSTANCE level to the DEPLOYMENT/APPLICATION | Yup, my guess would be we're then missing this | | | public AbstractScopeInfo(Object name, String className) | | { | | if (name == null) | | throw new IllegalArgumentException("Null scope"); | | | | ScopeKey scopeKey = ScopeKey.DEFAULT_SCOPE.clone(); | | scopeKey.addScope(CommonLevels.INSTANCE, name.toString()); | | if (className != null) | | scopeKey.addScope(CommonLevels.CLASS, className); | | setScope(scopeKey); | | setMutableScope(new ScopeKey(CommonLevels.INSTANCE, name.toString())); | | } | | So another fix would be to somehow make the Deployer's ScopeBuilder somehow aware of the class scope when it creates the component scope. Then there's no need for any merge. But there's probably a reason why I didn't do that in the first place (other than I just forgot - which might actually be the real reason. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185148#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...