"ALRubinger" wrote : "scott.stark(a)jboss.org" wrote : I think it should be the base jndi name, the equivalent of the jboss.xml jndi-name. | | jboss.xml jndi-name isn't a base..? | Its the remote home for ejb2, not sure what it has been used as for ejb3. "ALRubinger" wrote : | If the mappedName is a base name, then we can't bind anything directly to it. It'd be misleading for a bean provider to say "mappedName=MyBean" and then have to access "MyBean/remote". So mappedName should be similar to our @RemoteBinding handling, no? | | Carlo and I discussed this earlier, where mapped-name/jndi-name directly specify remote business binding, and all others use the default base. So given "mapped-name=MyBean" and a BasicJndiBindingPolicy: | | Default Remote Business Interface: "MyBean" | Remote Home: "ear/jar/ejb-name/home" | Remote Specific Business Interface: "ear/jar/ejb-name/remote-interfaceName" | In my view its similarly strange that there is no relationship to the other bindings. I see the issue with using a simple mappedName like MyBean not allowing uses like both MyBean and MyBean/home. I took a look at the glashfish ejb faq: https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html and it seems they have adopted a similar usage to have mappedName be the remote business interface, or at the level of xml its just the same as jndi-name for the reference global binding. So, remote business interface(s) proxy global jndi name it is. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164369#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...