NoAccessToFieldsAfterPredelete incorrectly mandates that field access to deleted instances will cause an error

• Key: JDO-413
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Minor
• Assignee: Craig Russell
• Reporter: Marc Prud'hommeaux
• Component/s: tck2
• Affects Version/s: JDO 2 final
• Fix Version/s: JDO 2 maintenance release 1, JDO 2 TCK challenge fixes

Description

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.

Comments

[Craig Russell]

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.

[Craig Russell]

svn commit -m "JDO-413 updated test to allow either exception or not for field access after preDelete" src/java/org/apache/jdo/tck/api/instancecallbacks/NoAccessToFieldsAfterPredelete.java
Sending src/java/org/apache/jdo/tck/api/instancecallbacks/NoAccessToFieldsAfterPredelete.java
Transmitting file data .
Committed revision 452640.

[Craig Russell]

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