| Craig Russell (JIRA) 2006-09-28, 7:11 am |
| [ http://issues.apache.org/jira/brows...action_12438411 ]
Craig Russell commented on JDO-413:
-----------------------------------
This issue is correct. The checks are not consistent with the JDO 2.0 specification. The patch is correct.
We should revisit this issue for JDO 2.1 to see if it makes sense for the checks to be added if the implementation is BinaryCompatible, or if another PersistenceManagerFactory flag would be suitable.
If there are no other comments, I'll check in the patch.
> NoAccessToFieldsAfterPredelete incorrectly mandates that field access to deleted instances will cause an error
> --------------------------------------------------------------------------------------------------------------
>
> Key: JDO-413
> URL: http://issues.apache.org/jira/browse/JDO-413
> Project: JDO
> Issue Type: Bug
> Components: tck20
> Affects Versions: JDO 2 final
> Reporter: Marc Prud'hommeaux
> Priority: Minor
> Attachments: NoAccessToFieldsAfterPredelete.java.patch
>
>
> org.apache.jdo.tck.api.instancecallbacks.NoAccessToFieldsAfterPredelete has 7 checks that assert that field access to fields in deleted instances will throw a JDOUserException, but section 5.5.7 only suggests that it *might* throw a JDOUserException: "A
ny other access to persistent fields is not supported and might throw a JDOUserException." The checks should not be there. The attached patch removes them.
--
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
|