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".
