StateTransitions test fails on detachCopy operation
---------------------------------------------------
Key: JDO-460
URL: https://issues.apache.org/jira/browse/JDO-460
Project: JDO
Issue Type: Bug
Components: tck2
Reporter: Michelle Caisse
Assigned To: Andy Jefferson
Fix For: JDO 2 maintenance release 1
StateTransitions fails on three cases for the detachCopy operation. These
transitions are newly specified for JDO 2.1. See JDO-456.
[java] There was 1 failure:
[java] 1)
test(org.apache.jdo.tck.lifecycle.StateTransitions)junit.framework.AssertionFailedError:
[java] Assertions A5.9-1 through A5.9-190 (StateTransitions) failed:
[java] StateTransitions: datastore transaction; current state hollow
[java] detachCopy with active datastore tx transitioned instance to invalid
state hollow; expected state persistent-clean
[java] Assertions A5.9-1 through A5.9-190 (StateTransitions) failed:
[java] StateTransitions: no transaction; current state hollow
[java] detachCopy outside tx with NontransactionalRead=false;
JDOUserException should have been thrown
[java] Assertions A5.9-1 through A5.9-190 (StateTransitions) failed:
[java] StateTransitions: no transaction; current state
persistent-nontransactional
[java] detachCopy outside tx with NontransactionalRead=false;
JDOUserException should have been thrown
[java]
[java] at org.apache.jdo.tck.JDO_Test.failOnError(JDO_Test.java:1103)
[java] at
org.apache.jdo.tck.lifecycle.StateTransitions.test(StateTransitions.java:414)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:254)
[java] at
org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108)
[java] at
org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148)
[java] at
org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
