
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
30/Apr/06 08:52 PM
|
|
In org.apache.jdo.tck.api.persistencemanager.DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager, Line 77: It should be pm2 instead of pm, otherwise cleanup of pm is skipped and a following test may fail. For instance running org.apache.jdo.tck.query.api.Close after DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager fails, because the old PCPoint instances are still there.
|
|
Description
|
In org.apache.jdo.tck.api.persistencemanager.DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager, Line 77: It should be pm2 instead of pm, otherwise cleanup of pm is skipped and a following test may fail. For instance running org.apache.jdo.tck.query.api.Close after DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager fails, because the old PCPoint instances are still there. |
Show » |
made changes - 30/Apr/06 08:43 PM
| Field |
Original Value |
New Value |
|
Affects Version/s
|
|
JDO 2 rc1
[ 12310771
]
|
|
Assignee
|
|
Michael Bouschen
[ mbo
]
|
|
Fix Version/s
|
|
JDO 2 final
[ 12310830
]
|
made changes - 30/Apr/06 08:52 PM
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
|
The name cleanupPM might be misleadinng, because the method does not clean up the database. It simply checks whether the transaction bound to the pm is still open and if yes calls rollback. Then it closes the pm. The database cleanup is done as part of method localTearDown implemented in the JDO_Test superclass and it will open a new new pm instance.