Rickard,
But the cache will be duplicated for each Session Bean instance that the
server starts, will it not?
This is almost certainly not the desired behavior. A CORBA or RMI object can
provide a real singleton for caching, or EJB servers may provide special
features in this area (e.g. GemStone/J's PCA).
-Chris.
> -----Original Message-----
> From: Rickard �berg [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, January 18, 2000 5:19 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Caching of read-only DB contents in an EJB
>
> Hey
>
> "Lahooti, Hamid" wrote:
> > 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.
>
> /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".
===========================================================================
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".
