08-09-07 06:11 PM
StateTransitionsReturnedObjects assumes Non Transactional Write enabled by d
efault
----------------------------------------------------------------------------
------
Key: JDO-514
URL: https://issues.apache.org/jira/browse/JDO-514
Project: JDO
Issue Type: Test
Reporter: Ilan Kirsh
StateTransitionsReturnedObjects fails with:
Assertions A5.9-1 through A5.5.8 (serialization, detachment, attachment) fai
led:
StateTransitionsReturnedObjects: no transaction; current state persistent-no
ntransactional-dirty
serialize outside tx; unexpected exception caught: com.objectdb.jdo._JDOUser
Exception: Attempt to modify an object with no active transaction when Nontr
ansactionalWrite is disabled: org.apache.jdo.tck.pc.lifecycle.StateTransitio
nObj#3
FailedObject:org.apache.jdo.tck.pc.lifecycle.StateTransitionObj@701a27
It seems that StateTransitionsReturnedObjects assumes non transactional writ
e enabled by default. Checking if the implementation supports non transactio
nal write is insufficient (when it is not the default setting).
An explicit:
pm.currentTransaction().setNontransactionalWrite(true);
is needed in getPersistentNontransactionalDirtyInstan
ce, 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.
[ Post a follow-up to this message ]
|