[
https://issues.apache.org/jira/browse/OPENJPA-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-732:
---------------------------------
Fix Version/s: (was: 1.3.0)
1.2.2
was fixed in 1.2.2 and trunk, not 1.3.0
> Updates to entities via Lifecycle callback methods
> ---------------------------------------------------
>
> Key: OPENJPA-732
> URL: https://issues.apache.org/jira/browse/OPENJPA-732
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2.1, 1.3.0
> Reporter: Kevin Sutter
> Assignee: Albert Lee
> Fix For: 1.2.2, 2.0.0-M2
>
> Attachments: OPENJPA-732-1.0.patch, OPENJPA-732-1.2.patch,
> openjpa-732-test.zip
>
>
> http://n2.nabble.com/Updates-to-entities-via-Lifecycle-callback-methods-td1110631.html
> In a nutshell, if we are to allow the updating of the entities passed into
> the Lifecycle callback methods, then we have a couple of problems (given the
> scenario of updating the entity passed into the @PreUpdate method):
> o The designated @Version field is getting updated more often than desired
> causing the transaction to rollback.
> o The @PostUpdate method is getting invoked more than once.
> I will post a testcase shortly. If and when we decide to fix this, this
> simple testcase will need to be expanded to include the updating of entities
> in other scenarios as well.
> I am also getting verification from the JPA Expert Group as to whether these
> entities are supposed to be updatable or not. As one of the dev postings
> indicated, our OpenJPA documentation indicates that they are updatable. But,
> the JPA spec itself is not clear on this capability. Other vendors, such as
> Hibernate, allow for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
