[ http://issues.apache.org/jira/browse/JDO-427?page=comments#action_12441221 ] Craig Russell commented on JDO-427: -----------------------------------
Since the spec is ambiguous, I'll change the test to UNSPECIFIED for element 11 and 12, for the branches/2.0.1 but not for the trunk. The maintenance release will move the sentence "If the parameter instance is detached, then JDOUserException is thrown" into the description of detach without an active transaction. And the test will verify that a detached-clean instance is returned as detached-clean, and a detached-dirty instance is returned as detached-clean. > StateTransitionsReturnedObjects incorrectly expects detachCopy() to allow > passing a detached instance > ----------------------------------------------------------------------------------------------------- > > Key: JDO-427 > URL: http://issues.apache.org/jira/browse/JDO-427 > Project: JDO > Issue Type: Bug > Components: tck20 > Affects Versions: JDO 2 final > Reporter: Marc Prud'hommeaux > Assigned To: Craig Russell > Priority: Minor > Fix For: JDO 2 maintenance release 1, JDO 2.0 TCK challenge fixes > > > Element 11 (0-based) of the "detachCopy with active tx" array in > org/apache/jdo/tck/lifecycle/StateTransitionsReturnedObjects.java asserts > that a detached instance passed to detachCopy() should result in its state > being unchanged. However, section 12.6.8 of the JDO 2 spec explicitly states: > "If the parameter instance is detached, then JDOUserException is thrown." > To fix it to check for the correct behavior, element 11 should be changed > from "UNCHANGED" to "ERROR". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
