"adrian(a)jboss.org" wrote : | Can you see if there is an easy way to issue a warning for this case? | Hmmm, I doubt it. Unless there is some flag on (Service)ControllerContext saying that we actually have a 'better' ControllerContext to access. Since the only things we do, are parse name from inject element - no knowlegde about ObjectName -, set this String name as underlying value to AbstractDependencyValueMetaData, then at ADVMD.getValue(TypeInfo, ClassLoader) do lookup by name (underlying value), which matches our mbean's ObjectName::getCanonicalName. And to get the actual bean, we just call ControllerContext::getTarget, not caring where it comes from. As you can see, it's your fault due to such ControllerContext abstraction. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169572#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...