IsTransactionalFalse makes invalid assumption that transaction is optimistic

• Key: JDO-409
• Type: Bug
• Status: Closed
• Resolution: Duplicate
• Priority: Major
• Assignee: Unassigned
• Reporter: Marc Prud'hommeaux
• Component/s: tck2
• Affects Version/s: JDO 2 final

Description

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();

Comments

[Ilan Kirsh]

I believe the title should be "IsTransactionalFalse makes invalid assumption that transaction is datastore" and that this issue duplicates JDO-400 that had already been fixed.

[Marc Prud'hommeaux]

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.

[Michael Bouschen]

Closed as a duplicate of JDO-400.