This is a vendor implementation issue. The spec clearly does not mandate
such a practice, and a quality CMP entity bean implementation would not do
that. There might be a vendor-specific workaround for your problem -- using
BMP instead of CMP(?) -- but I can't speculate further without knowing the
identity of your vendor.
<vendor>
The Persistence PowerTier EJB server (and at least a couple of other
vendors) have entity bean implementations where the container intelligently
updates only modified CMP beans in a transaction.
</vendor>
Hope this helps,
...Jim
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Aminadab Pereira Nunes
> Sent: Saturday, January 03, 1970 5:56 PM
> To: [EMAIL PROTECTED]
> 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".
