[
https://issues.apache.org/jira/browse/OPENJPA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey resolved OPENJPA-506.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.2
OpenJPA is now in line with the JPA spec's defined behavior. Additionally, new
instances that are persisted and then flushed and then modified, and existing
instances that are modified, flushed, and then modified again will receive
Pre/PostUpdate callbacks for the subsequent modifications.
> PreRemove method callback is never called; PreUpdate is always called
> ---------------------------------------------------------------------
>
> Key: OPENJPA-506
> URL: https://issues.apache.org/jira/browse/OPENJPA-506
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 1.1.0
> Environment: Windows XP, JDK1.5, JDK6, PostgreSQL
> Reporter: Miroslav Nachev
> Fix For: 1.0.2, 1.1.0
>
>
> I am using EntityListeners to catch Insert, Update and Delete events. During
> my test case I notice that PreRemove method callback is never called. In the
> same time PreUpdate is always called whether Delete (em.remove()) or Insert
> is called.
> In my opinion Pre/Post Persist must be called on Insert operations. Pre/Post
> Update must be called on Update operations. Pre/Post Remove must be called on
> Delete operations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
