[jira] Commented: (JDO-419) StateTransitions incorrectly asserts that field access in a deleted instance will throw an exception

["Marc Prud'hommeaux (JIRA)" <ji...@apache.org>]

    [ http://issues.apache.org/jira/browse/JDO-419?page=comments#action_12434323 ] 
            
Marc Prud'hommeaux commented on JDO-419:
----------------------------------------

This also affects the "read field with active optimistic transaction" state list. Another way to fix it is to change elements 7 & 8 from ERROR to IMPOSSIBLE in both the "read field with active optimistic transaction" and "read field with active datastore transaction" arrays.

> 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
>            Priority: Minor
>
> 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