Hi,
Joel Shellman wrote:
>
> 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?
Yes, JNDI is a nice way to do that. It sounds like a call for some kind
of JNDI-Connector. But notice the difference between this and the
"Enterprise Bean's Environment", which is also a JNDI context.
> How scalable is using JNDI for such purposes?
JNDI is one of the more (even the most) scalable technology for temp.
information storage. You can layer JNDI on RDBMS or LDAP servers.
> ie. what's the overhead of say looking up and getting
> "java:comp/env/my/object"?
looking up the initial context will be time consuming in most cases. But
it doesn't matter since you do it once and save the reference forever.
Looking up "java:comp/env/my/object" isn't expensive.
> Also, is that location writable by beans and
> clients (J2EE clients such as servlets and the like)?
Let clear the misunderstandings once more. I'm refering to a
JNDI-Connector, not the one used by the EJB server to provide the bean's
environment. Neither J2EE clients nor beans are allowed to write to the
bean environment.
/Francis.
--
[EMAIL PROTECTED]
MATHEMA Software GmbH
N�gelsbachstra�e 25 b
91052 E r l a n g e n
D e u t s c h l a n d
Tel +49(0)9131/8903-0
Fax +49(0)9131/8903-55
http://www.mathema.de
===========================================================================
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".
