| Marc Prud'hommeaux (JIRA) 2006-08-30, 7:11 am |
| Expectation of jdoPostLoad() invocation does not take into account the possibility of persistent-nontransactional state
-----------------------------------------------------------------------------------------------------------------------
Key: JDO-412
URL: http://issues.apache.org/jira/browse/JDO-412
Project: JDO
Issue Type: Bug
Components: tck20
Affects Versions: JDO 2 final
Reporter: Marc Prud'hommeaux
Priority: Minor
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. ModificationOfNontransactionalNonpersist
entFields.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);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|