[JDO-426] NullCollectionsAndIsEmpty does not unset mapped side of relation

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JDO 2 final (2.0)
• Fix Version/s: JDO TCK challenge fixes
• Component/s: tck
• Assignee: Michael Bouschen
• Reporter: A. Abram White
• Created: 14/Sep/06 21:32
• Updated: 14/Jun/10 11:08
• Resolved: 04/Oct/06 19:41

Description

org.apache.jdo.tck.query.jdoql.NullCollectionsAndIsEmpty uses its localSetUp() method to null the projects of an Employee. However, the Employee.projects field uses mapped-by in its mapping, and per section 15.3 of the JDO 2 spec, that means changes to it aren't reflected in the datastore. To fix, add the following lines after retrieving "emp1" but before nulling its projects in localSetUp():

for (Iterator itr = emp1.getProjects().iterator(); itr.hasNext()
((Project) itr.next()).removeMember(emp1);