[JDO-412] Expectation of jdoPostLoad() invocation does not take into account the possibility of persistent-nontransactional state

• Type: Bug
• Status: Closed
• Priority: Minor
• 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: Michael Bouschen
• Reporter: Marc Prud'hommeaux
• Created: 30/Aug/06 06:54
• Updated: 14/Jun/10 11:08
• Resolved: 03/Oct/06 19:57

Description

Some tests assume that jdoPostLoad() will be called, but do not take into account the possibilty that persistent-nontransactional is a valid state, and that jdoPostLoad() is not invoked for those instances. The solution should be to force instances to be transitioned to persistent-clean after commit by setting RetainValues=false.

This affects the following tests:

org.apache.jdo.tck.api.instancecallbacks.CallingJdoPostload.test
org.apache.jdo.tck.api.instancecallbacks.ModificationOfNontransactionalNonpersistentFields.test

The solution is to invoke "setRetainValues(false)" after obtaining the transaction in both the test cases. E.g.:

Transaction t = pm.currentTransaction();
t.setRetainValues(false);