What I'm currently working on is how we are redoing the ejb3 injection layer to be a generalized mc based version. The pieces are: - The MappedReferenceMetaDataResolverDeployer creates a map of endpoint names to resolved names in the top DeploymentUnit under the attachment name MappedReferenceMetaDataResolverDeployer.endpointMap. The endpoint names are of the forms: + "ejb/" + vfsPath + ejbName : for ejbs in the deployment + "ejb/" + vfsPath + local-interface name : for BusinessLocals + "ejb/" + vfsPath + remote-interface name : for BusinessRemotes + "message-destination/" + vfsPath + destName : for MessageDestinations - Each ee container creates KernelDeployment/BeanMetaData attachments for its components using a bean factory that ties into the container pooling. I'm fuzzy on the bean factory details in terms of whether the pooling is something that can live in the mc code. - DependencyInjectionDeployer wires the beans together using the MappedReferenceMetaDataResolverDeployer referencer to referencee mappings to add the dependencies to the component BeanMetaData. I'm currently looking at this in the context of the ejb2 deployer to see what issues show up for mixing mbean/mcbean components together. Once that is working the ejb3, client and war deployers can be updated in a similar fashion. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134884#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...