File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Websphere and the fly likes JNDI name for local lookup Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Head First Android this week in the Android forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "JNDI name for local lookup" Watch "JNDI name for local lookup" New topic

JNDI name for local lookup

Tulika Garg

Joined: Mar 27, 2009
Posts: 6

I am websphere newbie. I have a J2EE application that is written for JBoss and now I am trying to port it to WAS 7. I am using EJB 3.
I defined JNDI names for my local and remote interfaces in META-INF\jboss.xml
Now I want to do something similar for WAS so I can give the same JNDI names in WAS as I use in JBoss so I that need not change my code.

Say I have one stateless session bean and I have defined its local and remote JNDI names in jboss.xml as :


So after a bit of googling I found out about ibm-ejb-jar.bnd.xml
I defined my JNDI names in ibm-ejb-jar.bnd.xml as:
<session name="Authentication">
<interface class="" binding-name="CoreSvc/Authentication/remote"/>
<interface class="" binding-name="CoreSvc/Authentication/local"/>

But when I start this app in WAS, I get exception saying: The specific Java Naming and Directory Interface (JNDI) binding name provided for a local bean does not begin with ejblocal:. The CoreSvc/Authentication/local binding name that is specified for the Authentication bean in the CoreSvc.jar module does not begin with ejblocal:.

Is it necessary for JNDI names for local interface to begin with "ejblocal:" ?

I agree. Here's the link:
subject: JNDI name for local lookup
jQuery in Action, 3rd edition