bryan,
yes ... highly recommended. keep all references
cached. (eg: remote interface references of
stateless beans & home interfaces of stateful
beans/entity beans)
it is the container/ejb vendor's responsibility
to ensure safe access from multiple transactions/threads etc.
and lastly, cache not only in your servlet but in
your ejb's as well (say when ejbs lookup or 'use'
other ejbs)
-krish
----- Original Message -----
From: Bryan Field-Elliot <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 25, 2001 2:42 PM
Subject: Are home interface references thread-safe?
> I have a question about EJB home interface references, specifically
> about caching and re-using them:
>
> My "client" is a web application (servlet based), with many simultaneous
> users.
>
> Are they (home interface references) thread-safe? Can I do a home
> interface lookup at initialization time (as a singleton), and reuse it
> for each simultaneous user in my servlet?
>
> Thanks,
>
> Bryan
>
> ===========================================================================
> 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".
