I've re-edited my post. It's forum weirdness, because the text was still there. "alex.loubyansky(a)jboss.com" wrote : "Carlo" wrote : foo.ear/bar.jar/MyBean it will become "foo/MyBean" | | If we are going to follow this format then I don't see how the full JNDI name can be resolved on the metadata level. Since there is no info about parent deployment units. So, it seems like the JNDI name resolution is going to be split into the prefix and suffix parts (the later being resolved in the metadata). We must have a notion of parent deployment units at metadata level, because else we'll have a problem with the persistence unit deployer (EJB3 Persisitence 6.2.2 Persistence Unit Scope). "scott.stark(a)jboss.org" wrote : For 3 we need a utility class that properly looks at the reference type to determine if this is a home/local-home, remote or local, business interface lookup. Not really, you can just lookup "[ejbName]/[interface]". "ALRubinger" wrote : If we change the format "earName/jarName/beanName" to "earName/beanName", we lose the guarantee that the binding will be unique. Why remove "jarName" from here? Being inline with our own documentation. :-) We could change both. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147606#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...