You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Ilan Kirsh (JIRA)" <ji...@apache.org> on 2006/08/30 04:06:22 UTC
[jira] Commented: (JDO-409) IsTransactionalFalse makes invalid
assumption that transaction is optimistic
[ http://issues.apache.org/jira/browse/JDO-409?page=comments#action_12431434 ]
Ilan Kirsh commented on JDO-409:
--------------------------------
I believe the title should be "IsTransactionalFalse makes invalid assumption that transaction is datastore" and that this issue duplicates JDO-400 that had already been fixed.
> IsTransactionalFalse makes invalid assumption that transaction is optimistic
> ----------------------------------------------------------------------------
>
> Key: JDO-409
> URL: http://issues.apache.org/jira/browse/JDO-409
> Project: JDO
> Issue Type: Bug
> Components: tck20
> Affects Versions: JDO 2 final
> Reporter: Marc Prud'hommeaux
>
> The test IsTransactionalFalse.testIsTransactionalFalse mandates that an instance will be persistent-clean after a field is accessed in a transaction. However, when the transaction type is optimistic, it is also valid for the instance to be persistent-nontransactional after a field access.
> The test can be fixed by ensuring that the transaction is a datastore transaction. E.g.:
> public void testIsTransactionalFalse() {
> pm = getPM();
> Transaction tx = pm.currentTransaction();
> tx.setOptimistic(false); // make sure the transaction is not optimisitic
> tx.begin();
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira