Just to clarify, the java:/comp/env namespsace is read-only per the
EJB specification.
The server's JNDI tree is not read-only. After all, you can hot
deploy new EJBs.
-- Rob
On Sat, Aug 26, 2000 at 05:43:09PM -0700, Gene Chuang wrote:
> Hi,
>
> I believe Weblogic implements a "Read Only" JNDI service. After server
> initialization, you cannot bind anything to the JNDI tree.
>
> Gene
>
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> To: [EMAIL PROTECTED]
> Sent: 8/26/00 5:13 AM
> Subject: Re: How can JNDI be used in EJBs, servlets, etc?
>
> Joel,
>
> I don't believe that the EJB spec specifically precludes writing state
> information
> to the JNDI tree, in the form of serializable objects. However, if the
> application
> you are designing uses multiple EJB Server instances (for load balancing
> and/or
> failover), you may have a portability issue. For example, WebLogic
> synchronizes
> changes to the JNDI repository across servers in a cluster. BlueStone's
> JNDI
> service that runs in their UBS does not (they have a different
> mechanism, called
> a state server that is used to persist serialized objects). I'm not
> sure what approach
> other vendors take.
>
> So like many other things in EJB, the answer really depends on how
> important
> portability across EJB vendors is to your applications architecture.
>
> Hope this helps.
>
> > -----Original Message-----
> > From: Joel Shellman [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, August 25, 2000 11:43 AM
> > Subject: How can JNDI be used in EJBs, servlets, etc?
> >
> >
> > Not a strictly EJB question but rather how JNDI can be used for EJBs:
> >
> > This brings up a question I had. It seems to me I heard somewhere that
> > writing to the JNDI environment is either discouraged or disallowed. I
> > was thinking using JNDI for some synching and communication would be
> > very convenient. I also read just yesterday in a book suggesting using
> > JNDI for temporary storage of some information.
> >
> > Is it okay to use JNDI for temporary information storage/communication
> > or should that be avoided? How scalable is using JNDI for such
> purposes?
> > ie. what's the overhead of say looking up and getting
> > "java:comp/env/my/object"? Also, is that location writable by beans
> and
> > clients (J2EE clients such as servlets and the like)?
> >
> > Thanks,
> > --
> > Joel Shellman
> > Chief Software Architect
> > The virally-driven B2B marketplace for outsourcing projects
> > http://www.ants.com/90589781
> >
>
> ========================================================================
> ===
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
