"jaikiran" wrote : | I think the second example will be handled gracefully in 3.1 as per the specs (Section 4.4.1): | | anonymous wrote : Each portable session bean global JNDI name has the following syntax : | | | | java:global[/<app-name>]/<module-name>/<bean-name>#<fully-qualified-interface-name> | | | | The container registers a separate global JNDI name entry for each local business interface, each remote business interface, and any no-interface view, 2.x local home interface, or 2.x remote home interface. For the the no-interface view, the last portion of the entry name is the fully-qualified bean class name. | | | | The fully-qualified-interface-name will generate a unique JNDI name. | On second thoughts, Carlo is right. The following scenario will not work even in 3.1: Both packaged in same EAR/JAR: package org.myapp.business; | | @Stateless | public class ManagerBean implements org.myapp.Manager { | | } | package org.myapp.persistence; | | @Stateless | public class ManagerBean implements org.myapp.Manager { | | } | Both of these will resolve to java:global[/<app-name>]/<module-name>/ManagerBean#org.myapp.Manager | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183581#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...