
| Key: |
JDO-409
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Duplicate
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Marc Prud'hommeaux
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
10/Sep/06 08:01 PM
|
|
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();
|
|
Description
|
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();
|
Show » |
|
JDO-400that had already been fixed.