I agree with dim, and Util's getHome()/getLocalHome() should use
java:comp/env since that's the spec recommendation.

I suggest that we add getHomeJNDI()/getLocalHomeJNDI() methods that use the
JNDI name for lookup. This will make everybody happy. The javadocs in the
Util classes should explain the difference between the two and clearly state
that getHome()/getLocalHome() are the preferred methods for a container
environment.

I just saw Dion's response too. I disagree with his suggestion to resort to
JNDI if comp fails. That would be "defensive programming", which I don't
like because you wouldn't know why something works. IMHO different methods
is a better alternative.

Aslak

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dmitri
> Colebatch
> Sent: 31. januar 2002 23:02
> To: Jozsa Kristof; [EMAIL PROTECTED]
> Subject: Re: [Xdoclet-user] Generated Util classes' getHome()
>
>
> Christopher,
>
> there has been some discussion of this recently on dev (I think
> thats where it was).
>
> quick abc on jndi and ejb:  inside an ejb container, the spec
> "recommends" that a bean looks up resources in the java:comp/env
> namespace, and the container has to provide facilities for
> mapping references to other beans, datasources, etc. into that namespace.
> Each bean has its own java:comp/env namespace - that is to say
> that depending on your configuration, lookups in one java:comp/env
> namespace may or may not work elsewhere.
>
> so in short - the only reason that java:comp/env works is that
> the container makes it work - so, from outside the container,
> comp/env isn't going to work.  As you've noticed, looking up
> normally works fine.
>
> I cant remember what the direction the recent discussion took,
> but perhaps one of the other guys can chime in with some feedback on
> intended usage of the util classes - maybe you would like a
> remote util class?
>
> cheers
> dim
>
> ----- Original Message -----
> From: "Jozsa Kristof" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, February 01, 2002 8:53 AM
> 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


_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to