[ http://issues.apache.org/jira/browse/JDO-409?page=comments#action_12431472 ] Marc Prud'hommeaux commented on JDO-409: ----------------------------------------
You are correct about the title, and I agree that it is a duplicate. The fixed check in at http://svn.apache.org/repos/asf/db/jdo/trunk/tck20/src/java/org/apache/jdo/tck/api/jdohelper/IsTransactionalFalse.java looks correct to me. > IsTransactionalFalse makes invalid assumption that transaction is optimistic > ---------------------------------------------------------------------------- > > Key: JDO-409 > URL: http://issues.apache.org/jira/browse/JDO-409 > Project: JDO > Issue Type: Bug > Components: tck20 > Affects Versions: JDO 2 final > Reporter: Marc Prud'hommeaux > > The test IsTransactionalFalse.testIsTransactionalFalse mandates that an > instance will be persistent-clean after a field is accessed in a transaction. > However, when the transaction type is optimistic, it is also valid for the > instance to be persistent-nontransactional after a field access. > The test can be fixed by ensuring that the transaction is a datastore > transaction. E.g.: > public void testIsTransactionalFalse() { > pm = getPM(); > Transaction tx = pm.currentTransaction(); > tx.setOptimistic(false); // make sure the transaction is not > optimisitic > tx.begin(); -- 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
