[#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:

Repository	Revision	Date	User	Message
ASF	#454538	Mon Oct 09 22:42:57 UTC 2006	clr	~~JDO-419~~ ~~JDO-424~~ Changed state transition table to use UNSPECIFIED where the specification is unclear
				Files Changed
				MODIFY /db/jdo/trunk/tck20/src/java/org/apache/jdo/tck/lifecycle/StateTransitions.java MODIFY /db/jdo/branches/2.0.1/tck20/src/java/org/apache/jdo/tck/lifecycle/StateTransitions.java