Hi Marc, Thanks for submitting this bug report.
Would it be possible for you to attach a patch to the issue? That makes it a lot easier for one of the committers to test and check in the fix.
Thanks, Craig On Aug 29, 2006, at 5:05 PM, Marc Prud'hommeaux (JIRA) wrote:
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'hommeauxThe 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 optimisitictx.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
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
