if by "implicitly" you mean "by default", WebLogic certainly does this.
> -----Original Message-----
> From: Sriram Srinivasan [SMTP:[EMAIL PROTECTED]]
> Sent: Sunday, May 16, 1999 10:56 AM
> To: [EMAIL PROTECTED]
> Subject: Re: EJBs and the internet
>
> Ben Engber wrote:
>
> >
> > On the other hand, it seems like Entity Beans could handle in-memory
> > caching of data, greatly reducing SELECTs on the DB. But my
> implementation
> > (WebLogic) doesn't do this implicitly, which makes me wonder again, what
> > are they for?
>
> How do you mean "implicitly"? Weblogic's EJB implementation provides
> a caching/locking infrastructure for beans, exactly for the purpose
> of not having to go back to the db again if we can help it. There
> is nothing you as a bean programmer need to do except set bounds
> on the cache in the deployment descriptor.
>
> -Sriram
>
> ==========================================================================
> =
> 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".
