This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
Your guess is right, i am getting JNDI Naming exception. Ok i let you know what i have done,
1) I have deployed Session Bean and Servlet, into 1 web-application.
So i think's that's why it's giving JNDI Naming exception. Because Session Bean's when deployed under web-application are not recognised by GlassFish Server.
The possible solution that i can try is, today evening at home is to-
1) make Servlet deploy under Web-Application in Glassfish. 2) deploy Session bean under EJB modules in Glassfish.
So i think it's possible, that in Glassfish Server, 1 module component can call other module component's, so in my case, Web-application will call EJB module.
Please correct me, if my suggested solution is wrong somewhere.
S Bhanage
Greenhorn
Joined: Oct 28, 2009
Posts: 13
posted
0
Hi,
I think if you are getting JNDI Naming exception It might be becoz of the following
Here you have DI without specifying its 'name' field
(This will have default jndi lookup name)
Here you have again HelloUser (which means two differnt beans).