[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-6361) Collection events may contain wrong stored snapshot after merging a detached entity into the persistencecontext

[Gail Badner (JIRA)]

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

Gail Badner updated HHH-6361:
-----------------------------

    Issue Type: Patch  (was: Bug)

> Collection events may contain wrong stored snapshot after merging a detached entity into the persistencecontext
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HHH-6361
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6361
>             Project: Hibernate Core
>          Issue Type: Patch
>    Affects Versions: 3.6.5
>            Reporter: Erik-Berndt Scheper
>            Priority: Minor
>
> After the merge process, driven by the {{DefaultMergeEventListener}}, it can happen that the Hibernate collection events contain references to an incorrect stored snapshot. This is both the case for the {{PersistentCollection}} and the {{CollectionEntry}}, as returned by {{session.getPersistenceContext().getCollectionEntry(persistentCollection)}}
> By itself, this looks like a minor issue. However, this leads to severe problems when Envers is used. This bug causes HHH-6349, which results in inconsistent (invalid) audit trails and possibly AssertionFailures when the {{ValidityAuditStrategy}} is used. 
> I am pretty sure the same bug exists in the 4.0.0 Betas, since I have an Envers testcase for testng (3.6 branch) and junit4 (master) which both exhibit the same behaviour. However, I haven't looked in the changes in the merge process in 4.0.0 betas (compared to 3.6.x).
> I am currently preparing a testcase for the Hibernate testsuite (complimentary to the Envers testcases) together with a suggested fix, but this takes a bit more work than I anticipated.

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