Thinking more about this, the conflict can arise even when there are 2 beans with the same classname (but different package names) in the same jar.

Ex:

MyApp.ear/Single.jar

package org.myapp.business;

@Stateless
public class ManagerBean implements org.myapp.business.Manager {

}

package org.myapp.persistence;

@Stateless
public class ManagerBean implements org.myapp.persistence.Manager {

}

"wolfc" wrote:

The second example will even fail in 3.1, but I consider it bad practice to have two classes with the same name in 1 module.

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.

"ALRubinger" wrote:

Otherwise we could default the EJB Name to the FQN of the bean impl class, but I think that'll cause more problems (migration) that it'll solve.

"ALRubinger" wrote:

So the workaround is to set it explicitly.

"jaikiran" wrote:

I think the second example will be handled gracefully in 3.1 as per the specs (Section 4.4.1):

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.

package org.myapp.business;

@Stateless
public class ManagerBean implements org.myapp.Manager {

}

package org.myapp.persistence;

@Stateless
public class ManagerBean implements org.myapp.Manager {

}

java:global[/<app-name>]/<module-name>/ManagerBean#org.myapp.Manager

"ALRubinger" wrote:

There's no exception thrown when binding to an already bound address?

"jaikiran" wrote:


No exceptions in JBoss AS 4.2.3 GA.

Going by the logs looks like something to do with the org.jboss.ejb3.stateless.BaseStatelessProxyFactory which is doing with binding in 4.2.3 GA. Let me setup the 4.2.3 source code to dig more into this.

protected void bindProxy(Object proxy) throws NamingException
 {
 try
 {
 log.debug("Binding proxy for " + getContainer().getEjbName() + " in JNDI at " + jndiName);
 Util.rebind(getContainer().getInitialContext(), jndiName, proxy);
 } catch (NamingException e)
 {
 NamingException namingException = new NamingException("Could not bind stateless proxy with ejb name " + getContainer().getEjbName() + " into JNDI under jndiName: " + getContainer().getInitialContext().getNameInNamespace() + "/" + jndiName);
 namingException.setRootCause(e);
 throw namingException;
 }
 }

Okay :)