[ http://issues.apache.org/jira/browse/JDO-273?page=all ] Martin Zaun resolved JDO-273: -----------------------------
Resolution: Fixed Combined patch for JDO-273 and JDO-258 committed with revision 388087. The patch is based on Michael Watzek's patch for JDO-273 with a couple of modifications: - merged with latest JDO_Test.java, resolved conflicting changes - renamed class CheckStatesOfReturnedObjects to StateTransitionsReturnedObjects - changed classes StateTransitions and StateTransitionsReturnedObjects not to fail on the first error but to collect all error messages and test for failure at the end of test() - re-enacted the correct but commented state transitions currently failed by jpox (see Michael's comments above) - reviewed and fixed a number of failing state transitions with Craig - added a few cleanups There are a few action items left: - Review and clarify the state transition for argument instances of states 'hollow' and 'persistent-nontransactional' for serialize with active tx. Currently, the test expects for both, datastore and optimistic, tx a transition to 'persistent-clean'. Some discussion, however, has suggested that UNCHANGED should be the transition for optimistic tx. - File a jpox issue on the failing state transitions for argument instances (29 errors) and returned instances (19 errors). - There's a large amount of code duplication between classes StateTransitions and StateTransitionsReturnedObjects. File an issue for later cleanup and refactorization. > Create tests for sections 5.5.8 & 5.5.9, detachment lifecycle > ------------------------------------------------------------- > > Key: JDO-273 > URL: http://issues.apache.org/jira/browse/JDO-273 > Project: JDO > Type: Test > Components: tck20 > Versions: JDO 2 beta > Reporter: Matthew T. Adams > Assignee: Martin Zaun > Fix For: JDO 2 final > Attachments: JDO-273.patch > > Write tests for assertions in sections "5.5.8 Detached-clean", "5.5.9 > Detached-dirty". -- 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