Since it says that the entity bean is not invoked every time the client makes a
call and
minimizes our database access, thus, improving overall system
performance.
My question is, how the session bean comes to know whether to call the entity
bean method or send the data from the cache?
regards,
Ashish
Hemant Khandelwal wrote:
> Everytime a method on entity bean is called in some transaction context, the
> container calls ejbLoad to synchronize entity bean state with the dataBase.
> So its the containers responsibility to call ejbLoad method. In the bean you
> will write whatever state is there to synchronize.
>
> Hemant
> ----- Original Message -----
> From: "Ashish Deshpande" <>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, July 28, 2000 12:13 PM
> Subject: cache
>
> Hello,
>
> If we get the references to the home interface of the entity beans in
> setSessionContext() method of a stateless session bean, it says that
> the entity bean is not invoked every time the client makes a call and
> minimizes our database access, thus, improving overall system
> performance.
>
> But suppose there are many instances of the session bean, how these
> instances get notified whether there is a change in the database or not?
>
> regards,
> Ashish
>
> ===========================================================================
> 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".
