[OPENJPA-925] Bidirectional OneToOne relation incorrectly set in loadEagerJoin

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0, 1.2.1, 1.3.0, 2.0.0-M1, 2.0.0-M2
• Fix Version/s: 1.2.1, 1.3.0, 2.0.0-M2
• Assignee: Michael Dick
• Reporter: Catalina Wei
• Created: 18/Feb/09 06:43
• Updated: 09/Mar/10 18:31
• Resolved: 19/Feb/09 18:14

Description

A test scenario uncovers a bug in eager loading bidirectional OneToOne relation.

OneOneParent has a bidirectional OneToOne relation with OneOneChild as annotated as following:

@Entity
public class OneOneParent {
...
@OneToOne(mappedBy="parent")
private OneOneChild child;
}

@Entity
public class OneOneChild {
...
@OneToOne
private OneOneParent parent;
}

Testcase:

String query = "select c FROM OneOneChild c";
Query q = em.createQuery(query);
List list = q.getResultList();

for (int i = 0; i < list.size(); i++)

{ OneOneChild c = (OneOneChild) list.get(i); assertEquals(c, c.getParent().getChild()); }

We expect c equals c.getParent().getChild(), but instead got assertion failure.

It seems to be a bug introduced in performance improvement work (the related issues: OPENJPA-292 & OPENJPA-744).

Issue Links

• duplicates: OPENJPA-919 JUnit for Bi-directional OneToOne with null relationships
• is related to: OPENJPA-912 Potential NPE in setInverseRelation