[JDO-424] StateTransitions makes undocumented assertions in detachCopy with active tx

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JDO 2 final (2.0)
• Fix Version/s: JDO 2 maintenance release 1 (2.1), JDO TCK challenge fixes
• Component/s: tck
• Assignee: Craig L Russell
• Reporter: Marc Prud'hommeaux
• Created: 13/Sep/06 02:15
• Updated: 14/Jun/10 11:08
• Resolved: 09/Oct/06 22:43

Description

In StateTransitions.java, a couple of the transition assertions that are made in the "detachCopy with active tx" scenario are not documented:

Element 4 (0-based) asserts that HOLLOW will remain UNCHANGED when detachCopy() is called on them. However, this doesn't seem to be anywhere in the spec, and also doesn't seem right, since a hollow instance would need to instantiate its fields in order to cascade the detach operation (subject to the setting of the DETACH_LOAD_FIELDS setting).

Element 9 asserts that a PERSISTENT_NONTRANSACTIONAL instance will remain unchanged. However, for the same reason as above, it might transition to persistent-clean due to reading a field.