[hibernate-issues] [Hibernate-JIRA] Assigned: (HHH-5343) Issue with lazy loading of composite key for 1:1 entity relationships

Gail Badner (JIRA) noreply at atlassian.com
Sun Jul 11 18:08:14 EDT 2010


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

Gail Badner reassigned HHH-5343:
--------------------------------

    Assignee: Adam Warski

> Issue with lazy loading of composite key for 1:1 entity relationships
> ---------------------------------------------------------------------
>
>                 Key: HHH-5343
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5343
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: envers
>    Affects Versions: 3.5.1
>         Environment: hibernate-envers 3.5.1-Final, MySQL
>            Reporter: Jim O'Callaghan
>            Assignee: Adam Warski
>
> This issue was originally raised against envers 1.2.2.GA-hibernate-3.3, hibernate-core 3.3.1.GA, under the previous Envers JIRA at https://jira.jboss.org/browse/ENVERS-77 - a test case is attached to that Issue.  The problem is related to lazily loaded 1:1 entity relations using a composite key, where the Envers proxy for a key does not appear to load the key before persisting the containing entity, resulting in a problem when loading the contained entity back from the audit table.  The issue appears to still be present in hibernate-envers 3.5.1-Final.  Is there a known-workaround aprat from setting the contained entity to be eager loaded?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the hibernate-issues mailing list