Comments on: The Most Basic call EJB 3 from Servlet or JSP

By: Gardiary

Gardiary — Tue, 27 Oct 2009 00:34:33 +0000

Really kemal thanks for your information.
I Havent try something like that. It will be a good information for other..

Thanks,

By: kemal

kemal — Mon, 26 Oct 2009 11:26:21 +0000

Sorry, i don’t know how to post xml tags. I encoded it, i wish this work:

I added something like this into my web.xml file for my locale interface:

ejb/my/jndi/path/sb
Session

com.my.app.SBInterfaceLocal

And look up the EJB with the name “java:comp/env/ejb/my/jndi/path/sb”

By: kemal

kemal — Mon, 26 Oct 2009 11:19:28 +0000

Hi,

I’m sorry for this late reply.

I’m using Glassfish V2.1 in my project, too. And yes, it gives this exception. It also not related with deploying the EJB module, because i deploy my project as an enterprise application with all of its modules.

What i understand from searching google and my try outs is that if you use local interface you have to declare it in the web.xml file of the web module. There is no problem with the remote interfaces. The remote interfaces are automatically added to jndi.

I added something like this into my web.xml file for my locale interface:

ejb/my/jndi/path/sb
Session

com.my.app.SBInterfaceLocal

And look up the EJB with the name “java:comp/env/ejb/my/jndi/path/sb”

By: gardiary

gardiary — Mon, 26 Oct 2009 02:46:20 +0000

Have you deploy the EJB’s? It will look something like this, in your admin console:

By: TW

TW — Sun, 25 Oct 2009 14:53:13 +0000

I used glassfish 2.1 but… I still got this error

descriptionThe server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: PWC1391: Servlet.init() for servlet HelloEjb3Servlet threw exception
root cause

java.lang.RuntimeException: WEB5002: Exception in handleBeforeEvent.
root cause

com.sun.enterprise.InjectionException: Exception attempting to inject Unresolved Ejb-Ref ejb3.servlet.HelloEjb3Servlet/helloEjb@jndi: ejb3.bean.HelloEjb@null@ejb3.bean.HelloEjb@Session@null into class ejb3.servlet.HelloEjb3Servlet
root cause

javax.naming.NameNotFoundException: ejb3.bean.HelloEjb#ejb3.bean.HelloEjb not found

Could you pls advise me? Thanks

By: Gardiary

Gardiary — Mon, 07 Sep 2009 04:22:05 +0000

What is your application server? Calling EJB 3 using JNDI lookup isn’t the same between Application Server.

If u use glassfish, u shoudn’t get an error.

By: kemal

kemal — Fri, 04 Sep 2009 15:02:09 +0000

Hi,

i got the error below when using jndi lookup on jsp. can you help me about what am i doing wrong.

i have a local interface called RegisterService and a bean implementation called RegisterServiceBean, both in the same package, session. they are just simple as the ones in your example and i try to use jndi lookup just like the jsp example you gave above. however, i’m getting the error below.

error:

javax.naming.NameNotFoundException: session.RegisterService not found
at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:216)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:188)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:74)
at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:111)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:409)
at javax.naming.InitialContext.lookup(InitialContext.java:392)