This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
I have a scenario where in I"m doing a lookup for a Stateless session bean. This Stateless session bean extends an abstract class and in the abstract class i"m doing some DI on some resources using the @Resource annotation. Now what happens is, when I deploy this to my Weblogic, it goes off fine and when I try to access this SSB, I run into a NamingException. The JNDI path for the resource that I"m injecting in my abstract class is something like x.y.z.myAbstractClass#myAbstractClass and the JNDI name of the SSB is something like x.y.u.mySSB#mySSB. When I look at the stact trace, it says that unable to resolve x.y.u.mySSB#mySSB, resolved till x.y.
After having a look at this I started to think that this might be because of the DI which might have failed in the abstract class. But there is no way for me to check this. I tried seeing the JNDI tree but everytime I try to view it my system crashed and I really did not want to waste time on that. So ranchers is my guess correct? because I remember form the specs that if the DI fails then the bean instance is discarded. But does DI happens during deployment or during run time?
SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!