| Marc Prud'hommeaux (JIRA) 2006-09-13, 1:11 am |
| [ http://issues.apache.org/jira/brows...action_12434333 ]
Marc Prud'hommeaux commented on JDO-419:
----------------------------------------
My opinion is that it is useful to be left up to the vendor to decide whether to throw an exception or not (or only throw an exception if the field is hollow).
> 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
> Attachments: 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. Howeve
r, 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/secur...nistrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|