db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JDO-424) StateTransitions makes undocumented assertions in detachCopy with active tx
Date Mon, 09 Oct 2006 22:44:22 GMT
     [ http://issues.apache.org/jira/browse/JDO-424?page=all ]

Craig Russell resolved JDO-424.

    Resolution: Fixed

svn commit -m "JDO-419 JDO-424 Changed state transition table to use UNSPECIFIED where the
specification is unclear" trunk/tck20/src/java/org/apache/jdo/tck/lifecycle/StateTransitions.java
Sending        branches/2.0.1/tck20/src/java/org/apache/jdo/tck/lifecycle/StateTransitions.java
Sending        trunk/tck20/src/java/org/apache/jdo/tck/lifecycle/StateTransitions.java
Transmitting file data ..
Committed revision 454538.

> StateTransitions makes undocumented assertions in detachCopy with active tx
> ---------------------------------------------------------------------------
>                 Key: JDO-424
>                 URL: http://issues.apache.org/jira/browse/JDO-424
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Marc Prud'hommeaux
>         Assigned To: Craig Russell
>             Fix For: JDO 2 maintenance release 1, JDO 2.0 TCK challenge fixes
> In StateTransitions.java, a couple of the transition assertions that are made in the
"detachCopy with active tx" scenario are not documented:
> Element 4 (0-based) asserts that HOLLOW will remain UNCHANGED when detachCopy() is called
on them. However, this doesn't seem to be anywhere in the spec, and also doesn't seem right,
since a hollow instance would need to instantiate its fields in order to cascade the detach
operation (subject to the setting of the DETACH_LOAD_FIELDS setting).
> Element 9 asserts that a PERSISTENT_NONTRANSACTIONAL instance will remain unchanged.
However, for the same reason as above, it might transition to persistent-clean due to reading
a field.

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


View raw message