[#JDO-431] StateTransitionsReturnedObjects assumes serializing/deserializing persistent-nontransactional-dirty instances results in transient instances

JDO

StateTransitionsReturnedObjects assumes serializing/deserializing persistent-nontransactional-dirty instances results in transient instances

Created: 04/Oct/06 03:28 PM Updated: 10/Oct/06 07:45 PM

Return to search

Component/s:

tck2

Affects Version/s:

JDO 2 final

Fix Version/s:

JDO 2 TCK challenge fixes

Time Tracking:

Not Specified

Resolution Date:

10/Oct/06 07:45 PM

Description

« Hide

This is part of TCK challenge 10.

Element 10 of "serialize outside tx" asserts that a persistent-nontransactional-dirty instance will become transient after serialize/deserialize, even though the specification seems to never mandate this. detached-clean should be an equally valid assertion.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Craig Russell added a comment - 04/Oct/06 03:29 PM

I agree that this behavior is not specified, and until the proper behavior is specified, the test case should be changed to UNSPECIFIED for this case.

I'll bring up a discussion with the expert group on the proper specified behavior here.

[ Permlink | « Hide ]

Craig Russell added a comment - 10/Oct/06 07:45 PM

svn commit src/java/org/apache/jdo/tck/lifecycle/StateTransitionsReturnedObjects.java
Sending src/java/org/apache/jdo/tck/lifecycle/StateTransitionsReturnedObjects.java
Transmitting file data .
Committed revision 462525.