No, from the "jndi name issues" thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=134618 and the last tck call, we seemed to agree on the container having a jndi name, and the proxies accessible under jndi-name/interface-name with the special interface-names home, remote, local, local-home for the legacy 2.1 views. We still need a getResolvedJndiName on the JBossEnterpriseBeanMetaData if we are going this route, but was waiting to see if it was doable. Carlo had a question on whether or not this would be handled correctly by the proxy layer and associated jndi object name factory binding. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148702#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...