[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-6753) Envers WorkUnits: Problems with merge

[Adam Warski (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Warski resolved HHH-6753.
------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0.0.next

> Envers WorkUnits: Problems with merge
> -------------------------------------
>
>                 Key: HHH-6753
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6753
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: envers
>    Affects Versions: 3.6.2
>            Reporter: S M
>            Assignee: Lukasz Antoniak
>             Fix For: 4.0.0.next
>
>
> As Hibernate triggers a commit, the Envers-Listener notices a DELETE followed by an ADD for the same entity (that's how my code is working...). I'd expect that Envers creates an UPDATE-Revision for this entity. But the AuditProcess tries to merge both actions and ends up with no action. Hence, no revision is written into the revision table. This is due to the fact that DelWorkUnit.merge(AddWorkUnit) returns NULL.
> So why is that? Why is this method not returning a new ModWorkUnit?
> http://community.jboss.org/thread/173930

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira