This week's book giveaway is in the Performance forum. We're giving away four copies of The Java Performance Companion and have Charlie Hunt, Monica Beckwith, Poonam Parhar, & Bengt Rutisson on-line! See this thread for details.
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:
<interface class="com.adobe.apss.services.AuthenticationRemote" binding-name="CoreSvc/Authentication/remote"/>
<interface class="com.adobe.apss.services.AuthenticationLocal" binding-name="CoreSvc/Authentication/local"/>
But when I start this app in WAS, I get exception saying:
com.ibm.ejs.container.EJBConfigurationException: 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:" ?