I had the same problem. It looks like the <jndi-name> element is totally ignored in the deployment descriptor.
What you will find however is that OpenEJB automatically creates JNDI entries for your EJBs Remote and Local interfaces automatically using the default names. I bet if you try looking up "MyBeanRemoteHome" instead of "MyBean", you will find your EJB. weberjn wrote: > > Hi, > > I try to access a 2.1 style EJB in Geronimo 2.1 (with xml deployment > descriptors) > > I defined this JNDI name in openejb.xml > > <enterprise-beans> > <session> > <ejb-name>MyBean</ejb-name> > <jndi-name>MyBean</jndi-name> > > I tried a JNDI lookup from a Java client using these properties: > > java.naming.factory.initial=org.openejb.client.RemoteInitialContextFactory > java.naming.provider.url=localhost:4201 > java.naming.security.principal=system > java.naming.security.credentials=manager > > > I tried to look up "MyBean" in an InitialContext: > > Caused by: javax.naming.NameNotFoundException: /MyBean does not exist in > the system. Check that the app was successfully deployed. > > With "java:MyBean": > > javax.naming.NameNotFoundException: MyBean does not exist in the system. > Check that the app was successfully deployed. > > I would guess that the one specified with <jndi-name> would be correct, > but this isn't so. > > What is the right JNDI name? > > Thanks, > Juergen > > > > -- View this message in context: http://www.nabble.com/JNDI-name-for-Java-client-to-2.1-EJB-tp18835233s134p18836702.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
