[#JDO-419] StateTransitions incorrectly asserts that field access in a deleted instance will throw an exception

JDO

StateTransitions incorrectly asserts that field access in a deleted instance will throw an exception

Created: 06/Sep/06 08:33 AM Updated: 09/Oct/06 10:43 PM

Return to search

Component/s:

tck2

Affects Version/s:

JDO 2 final

Fix Version/s:

JDO 2 maintenance release 1, JDO 2 TCK challenge fixes

Time Tracking:

Not Specified

File Attachments:

File Name	Date Attached	Attached By	Size
JDO-419.patch	2006-10-04 12:18 AM	Craig Russell	2 kB
JDO-419.patch	2006-09-12 11:58 PM	Marc Prud'hommeaux	0.7 kB

Resolution Date:

09/Oct/06 10:43 PM

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Marc Prud'hommeaux made changes - 12/Sep/06 11:58 PM

Field	Original Value	New Value
Attachment		JDO-419.patch [ 12340699 ]

Craig Russell made changes - 13/Sep/06 12:08 AM

Assignee

Craig Russell [ clr ]

Craig Russell made changes - 04/Oct/06 12:18 AM

Attachment

JDO-419.patch [ 12342226 ]

Craig Russell made changes - 04/Oct/06 09:22 PM

Fix Version/s		JDO 2.0 TCK challenge fixes [ 12312093 ]
Fix Version/s		JDO 2 maintenance release 1 [ 12310923 ]

Craig Russell made changes - 09/Oct/06 10:43 PM

Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Resolved [ 5 ]