[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2277) bidirectional <key-many-to-one> both lazy=false fetch=join lead to infinite loop

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2277?page=c... ] Steve Ebersole commented on HHH-2277: ------------------------------------- Findings: This appears to be limited to sceanrios where (1) the composite pk is non-embedded and (2) the eager fetching is defined at the metadata level and (3) the entity retrieval is attempted via a load. As a few examples of extra tests I ran that *did* work: 1) Using the same metadata, etc as org.hibernate.test.keymanytoone.KeyManyToOneTestCase 1.a) eager fetching via HQL 1.b) eager fetching via Criteria 2) Using the same metadata as org.hibernate.test.keymanytoone.KeyManyToOneTestCase except for non-laziness on the key-many-to-one mappings, all access paths worked. 3) Using an embedded composite identifier (instead of a pk-class) all access paths worked. Thus it would appear that there exists some difference in how UniqueEntityLoader#load operates as compared to the more generic Loader#doQueryAndInitializeNonLazyCollections which causes this problem. My initial attempts to fix centered on the ComponentType#resolve method, which met with limited success. The assumption there being that the issue stems from the fact that components do not take advantage of two-phase loading. -- 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