"heiko.braun(a)jboss.com" wrote : | Currently we use the MC kernel todo a lookup by name, which uses the legacy ObjectName. | Ok, are we comfortable as that as the lookup mechanism? We can make sure its available on the JBossEnterpriseBeanMetaData. "heiko.braun(a)jboss.com" wrote : | anonymous wrote : | | DeploymentScope.getEjbContainer(String ejbLink, Class businessIntf, String vfsContext) works for the ejb-name. | | | | Does this mean I can simply use the ejb-name for ejb-link and thus resolve the corresponding container? If that's the case, then I am all set. That is what could be used now, but the problem with resolving the name is that its not unique. If for a given ejb deployment, you use its local ejb-names this will just work. What I also proposed was ensuring the container name was made available on the JBossEnterpriseBeanMetaData, and DeploymentScope would support lookup of the EJBContainer by that name. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147999#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...