|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
10/Oct/06 05:50 PM
|
|
Element 10 (0-based) of the "makePersistent" array in org/apache/jdo/tck/lifecycle/StateTransitionsReturnedObjects.java asserts that a detached-clean instance passed to makePersistent() should have the resulting object be in the "persistent-clean" state. However, section 12.6.7 of the JDO 2 spec merely says that: "During application of changes of the detached state, if the JDO implementation can determine that there were no changes made during detachment, then the implementation is not required to mark the corresponding instance dirty." Based on this, it should be legal for the object to be in either the hollow state as well as the persistent-clean state.
The easiest fix, short of changing the test case to allow for multiple states, is to change element 10 from "PERSISTENT_CLEAN" to "IMPOSSIBLE", which will disable the state check altogether.
|
|
Description
|
Element 10 (0-based) of the "makePersistent" array in org/apache/jdo/tck/lifecycle/StateTransitionsReturnedObjects.java asserts that a detached-clean instance passed to makePersistent() should have the resulting object be in the "persistent-clean" state. However, section 12.6.7 of the JDO 2 spec merely says that: "During application of changes of the detached state, if the JDO implementation can determine that there were no changes made during detachment, then the implementation is not required to mark the corresponding instance dirty." Based on this, it should be legal for the object to be in either the hollow state as well as the persistent-clean state.
The easiest fix, short of changing the test case to allow for multiple states, is to change element 10 from "PERSISTENT_CLEAN" to "IMPOSSIBLE", which will disable the state check altogether. |
Show » |
| There are no subversion log entries for this issue yet.
|
|
Bug
Resolved
Minor
StateTransitionsReturnedObjects disallows makePersistent() on a detached-clean instance from being hollow
