That I understand. What I Don't get is why its needed? If I set up a cluster
of front-end jsp/servlet, and a cluster of ejb servers, because they are all
using Orion, I want my front-end servlets to access the middle-tier ejbs.
For this..do I need JNDI properties to find the EJBs? Or..as I think I
understood from some others..because they are all running Orion, this is not
needed, and I only have to do a Context context = new InitialContext();
xxx.lookup("..."); and so on like all the examples I see? I am not talking
about a client outside the scope of a web-app, that I understand you need
the jndi properties. I mean..inside my web-app, but not running on the same
server (or the same cluster), will I have to use jndi properties or not?
Thanks.
> -----Original Message-----
> From: Tim Endres [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 16, 2000 1:41 PM
> To: Orion-Interest
> Subject: Re: JNDI Properties for Orion and EJB?
>
>
> > Hi there,
> >
> > I read in my EJB book that CTM's require vendor specific
> JDNI properties. I
> > thought EJB was platform/vendor independent? What are these
> JNDI properties
> > for? More importantly..when/why are they used? I see in the
> example EJB's
> > with Orion that they all have a jndi.properties file, yet I
> am not quite
> > sure how to understand them.
>
> The JNDI properties is what helps make your code EJB independent.
>
> The file specifies the information specific to access your
> EJB container's
> namespace. By putting this information (factory class,
> principal (user),
> credentials (password)) in the properties file, you avoid
> hard-coding it.
>
> tim.
>
