Re: Caching of read-only DB contents in an EJB

[Rickard �berg]

Hi!

"Lahooti, Hamid" wrote:
> > A stateless session bean with a state?
> >>Yes. If it's readonly and not client specific. Sure.
> > as a singleton?
> >>I didn't say that.
> I did. It is needed for managing caches.
> Containers can destroy stateless session beans when they
> decide they are not needed by clients. IMHO, that's not
> a good foundation for implementing a cache manager.

If the state is kept in instance variables, and it is "heavy", this will
be a problem, but only if the server creates/destroys instance often. If
the size of the pool is set to the approximate nr of concurrent callers
this will not be a problem.

If the state is threadsafe you could easily use a static variable to
keep the data. Just be prepared to reload it if the server discards the
class.

/Rickard

--
Rickard �berg

@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality

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