[ http://issues.apache.org/jira/browse/JDO-419?page=all ]
Craig Russell resolved JDO-419.
-------------------------------
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
branches/2.0.1/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 incorrectly asserts that field access in a deleted instance
> will throw an exception
> ----------------------------------------------------------------------------------------------------
>
> Key: JDO-419
> URL: http://issues.apache.org/jira/browse/JDO-419
> Project: JDO
> Issue Type: Bug
> Components: tck20
> Affects Versions: JDO 2 final
> Reporter: Marc Prud'hommeaux
> Assigned To: Craig Russell
> Priority: Minor
> Fix For: JDO 2 maintenance release 1, JDO 2.0 TCK challenge fixes
>
> Attachments: JDO-419.patch, JDO-419.patch
>
>
> The series of states marked with "read field with active datastore
> transaction" (element 14 of the "transitions" field of
> org.apache.jdo.tck.lifecycle.StateTransitions) asserts that accessing a field
> of a deleted instance will throw an exception. However, this is not mandated
> by the spec, only suggested that it might happen. Section 5.5.6 reads: "Any
> other access to persistent fields is not supported and might throw a
> JDOUserException".
> The only easy fix is to just remove the "read field with active datastore
> transaction" test specifications.
--
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
