[jboss-dev-forums] [Design of EJB 3.0] - Re: Default JNDI naming scheme in EJB3.0 and possible confli

[jaikiran]

"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. 

Found this in org.jboss.ejb3.stateless.BaseStatelessProxyFactory

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;
  |       }
  |    }

For some reason Util.rebind is being used instead of Util.bind. That explains why the exception is not thrown.

Do you think it was intentional to use rebind for some reason? If not, do you want me to create a JIRA to fix this?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184131#4184131

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184131