Hello
> Caching requires singleton capability that ejb does not currently offer.
> You best (only) bet is to use CORBA/RMI server and delegate
> the property read operations from your ejb to the cache server.
> You will then have to worry about how to maintain the cache in sync
> with the database.

>>Almost but not quite. Readonly data can be cached by stateless session
>>beans. If you need read/write caching then either use Entities or a RMI
>>object.

A stateless session bean with a state? as a singleton? and it
doesn't get destroyed by the container?

Hamid

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

Reply via email to