java:comp/env is a magic namespace for each bean. Thus, if you are outside of the bean you will not see that special context. This allows for the same ejb-ref name to point to different real names without having a conflict:
Bean1: java:comp/env/Account -> com.foo.Account Bean2: java:comp/env/Account -> com.bar.Account Dion > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Jozsa > Kristof > Sent: Thursday, January 31, 2002 2:53 PM > To: [EMAIL PROTECTED] > Subject: [Xdoclet-user] Generated Util classes' getHome() > > > Hello, > > using the generated *Util classes, it seems that their getHome() methods > fail when they're invoked 'outside' of the EJB environment. As I see if I > get the home manually (getting InitialContext, doing lookup and narrow the > home class), and use the classes' JNDI_NAME, it works fine, but fails using > COMP_NAME, and unfortunately the *Util classes defaults to that. > > I'm still not an EJB expert, so I cant really explain why the beans don't > get bounded into 'java:comp/env/ejb/', I only see that using the plain > JNDI_NAME would be fine for me. Is there any way to change the generated > Util classes behaviour from an xdoclet tag or somehow else; or shall I do > something else to get my beans working with the current settings? > > All that happens on JBoss3, last working snap, the exact error at getHome() > invocation is: 'javax.naming.NameNotFoundException: comp not bound' > > Christopher > -- > .Digital.Yearning.for.Networked.Assassination.and.Xenocide > > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user > _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
