
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
04/Oct/06 07:41 PM
|
|
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);
|
|
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);
|
Show » |
| No work has yet been logged on this issue.
|
|