[jboss-user] [JNDI/Naming/Network] - Re: New EJB causes JNDI failure on existing EJB?

hmccartney do-not-reply at jboss.com
Thu Dec 13 06:23:38 EST 2007

Thanks very much for your reply.

The lookup is being done after the deployment of the application.

Both applications on both machines are packaged as ears containing several ejb3 and jar files. So on machine 2 we have MyApp1.ear and MyApp2.ear. MyWorkerBean is in Worker.ejb3 inside MyApp1.ear.

I should have said that in MyWorkerBean I have specified the JNDI name with:
public @Stateless
  | @TransactionAttribute(value = TransactionAttributeType.REQUIRES_NEW)
  | @RemoteBinding(jndiBinding = "MyWorkerBean/remote")
  | class MyWorkerBean implements MyWorker {

Does the rule about prefixing the JNDI name with the name of the ear still apply in this case? 

I don't have access to the test system at the minute but I'll try using 
MyWorker myWorker = (MyWorker) context.lookup("MyApp1/MyWorkerBean/remote");
instead as soon as I get the chance. I'll also double-check the JNDI tree in the JMX console.

Thanks again for your suggestions.



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

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

More information about the jboss-user mailing list