Beans are updated at transaction boundaries, so your bean should always
reflect the state of the data store per transactional view.
This can be relaxed depending on what sort of caching policies your
container supports. That is a question for the EJB server vendor you are
using.
Regards,
-Chris.
> -----Original Message-----
> From: Patrick Balm [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, December 03, 1999 3:44 AM
> To: [EMAIL PROTECTED]
> Subject: Entity bean data update
>
> Fellow developers,
>
> I am in the process of setting up the EJB environment for my current
> project.
> I am curious about the following.
>
> If an Entity bean is created (in memory) and I have a process
> running in a Legacy system application which changes the exact same data
> that
> my EJB has a reference to.
> Will the Container notice this change and update the persistent data in
> the bean
> (even when passivated) or will it do this on the fly (when the bean is
> called again by the client)?
>
> Thanks in advance.
>
> Kind regards,
>
> P@rick Balm.
>
> JNet Consultancy BV
> Socratestuin 5
> 2908 XC Capelle a/d IJssel
> tel +31 10 227 1648
> fax +31 10 227 1649
>
> Patrick Balm
>
> [EMAIL PROTECTED]
> mobile +31 655 107749 << File: C:\TEMP\nsmail85.jpeg >>
> http://www.jnc.nl>
>
>
===========================================================================
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".
