If you are using Weblogic you could try looking at the "IsModified"
extension. This is non-standard though!
Simon.
----- Original Message -----
From: Aminadab Pereira Nunes <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, January 03, 1970 11:56 PM
Subject: Container managed persistence aspects
> Hi there,
>
>
> I've got a question about entity beans with container-managed
> perisistence. In tests I notice that when you invoke an entity bean's
> access method (I mean a method that doesn't change the bean's
> attributes) within a transaction the container updates the bean's state
> at the database. In other words, if you access an entity bean, even
> without changing it, within a transaction, the rows that map this bean
> on the database are updated.
>
> Is it really supposed to be like that or is there somehow to specify
> that the bean's state hasn't been changed, and therefore doesn't need to
> be updated on the database ?
>
>
> thks for any help,
>
>
> --
> Aminadab
> email: [EMAIL PROTECTED]
>
>
===========================================================================
> 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".
