[jira] Resolved: (JDO-514) StateTransitionsReturnedObjects assumes Non Transactional Write enabled by default

["Michelle Caisse (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JDO-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michelle Caisse resolved JDO-514.
---------------------------------

       Resolution: Fixed
    Fix Version/s: JDO 2 maintenance release 1
         Assignee: Michelle Caisse

Revision 583887

> StateTransitionsReturnedObjects assumes Non Transactional Write enabled by default
> ----------------------------------------------------------------------------------
>
>                 Key: JDO-514
>                 URL: https://issues.apache.org/jira/browse/JDO-514
>             Project: JDO
>          Issue Type: Test
>            Reporter: Ilan Kirsh
>            Assignee: Michelle Caisse
>             Fix For: JDO 2 maintenance release 1
>
>
> StateTransitionsReturnedObjects fails with:
> Assertions A5.9-1 through A5.5.8 (serialization, detachment, attachment) failed: 
> StateTransitionsReturnedObjects: no transaction; current state persistent-nontransactional-dirty
> serialize outside tx; unexpected exception caught: com.objectdb.jdo._JDOUserException: Attempt to modify an object with no active transaction when NontransactionalWrite is disabled: org.apache.jdo.tck.pc.lifecycle.StateTransitionObj#3
> FailedObject:org.apache.jdo.tck.pc.lifecycle.StateTransitionObj@701a27
> It seems that StateTransitionsReturnedObjects assumes non transactional write enabled by default. Checking if the implementation supports non transactional write  is insufficient (when it is not the default setting).
> An explicit:
>   pm.currentTransaction().setNontransactionalWrite(true);
> is needed in getPersistentNontransactionalDirtyInstance, before:
>   obj.writeField(10000);

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.