[ http://issues.apache.org/jira/browse/JDO-413?page=all ]
Craig Russell resolved JDO-413.
-------------------------------
Fix Version/s: JDO 2 maintenance release 1
JDO 2.0 TCK challenge fixes
Resolution: Fixed
svn commit -m "JDO-413 updated test to allow either exception or not for field
access after preDelete"
../../branches/2.0.1/tck20/src/java/org/apache/jdo/tck/api/instancecallbacks
Sending
branches/2.0.1/tck20/src/java/org/apache/jdo/tck/api/instancecallbacks/NoAccessToFieldsAfterPredelete.java
Transmitting file data .
Committed revision 452641.
The patch has been committed to the trunk and branch 2.0.1
> 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
> Assigned To: Craig Russell
> Priority: Minor
> Fix For: JDO 2 maintenance release 1, JDO 2.0 TCK challenge fixes
>
> 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: "Any 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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
