[hibernate-issues] [Hibernate-JIRA] Created: (HHH-5845) Lazy Loading of audited entites with revision type 'delete'

Lazy Loading of audited entites with revision type 'delete' ----------------------------------------------------------- Key: HHH-5845 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5845 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.6 Environment: Hibernate 3.5.6, Oracle 10 DB Reporter: Jonas Schlaak Two classes are given, and they are related via a OneToOne relationship: @Audited public class MyClass { @OneToOne @Cascade(value = CascadeType.ALL) private MyOtherClass otherClass; } @Audited public class MyOtherClass { } The property "org.hibernate.envers.store_data_at_delete" is set to true, and when auditquerying for the deleted objects and initiliazing the otherClass (an entity which is also deleted) property, and ObjectNotFoundExceptions is thrown. It seems that the proxies do not look for deleted entities, because the same query works fine for the entities of revision type 'ADD' and 'MOD'. The code of the query: AuditQuery queryDeleted = reader.createQuery().forRevisionsOfEntity( MyClass.class, false, true).add( AuditEntity.revisionType().eq(RevisionType.DEL)); List queryResult = queryDeleted.getResultList(); List<MyClass> result = new ArrayList<MyClass>(); for (Object object : queryResult) { Object[] oArray = (Object[]) object; MyClass c = (MyClass) oArray[0]; Hibernate.initialize(c.getOtherClass()); } Forum post with Adam Warski's response: http://community.jboss.org/thread/160939?tstart=0 -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira