Where I'm at right now is: - The MappedReferenceMetaDataResolverDeployer creates a mapping of the endpoint ids (ejb/vfspath/ejbName, etc) to a ContainerDependencyMetaData. There still is a layer of mapping with alternative keys as has been talked about here for resolving references, but the output is the unique set of ContainerDependencyMetaData for referenced endpoints. - The ContainerDependencyMetaData has the set of ResourceInjectionTargetMetaData for references that need the endpoint injected. - The ContainerDependencyMetaData has the jndi names that references have declared they will lookup rather than inject. - The ContainerDependencyMetaData has the container name and bean factory which have to be setup by the associated endpoint deployer. The associated container bean also has aliases for the jndi names associated with the endpoint. There can be more than one due to different invokers (ejb2). I assume there is something similar for ejb3, but I'm not that far yet. Getting this wired up to validate it works in the ejb2/3 deployers is something I'm still working on. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136688#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...