| Michael Bouschen (JIRA) 2006-04-30, 1:11 pm |
| [ http://issues.apache.org/jira/browse/JDO-376?page=all ]
Michael Bouschen resolved JDO-376:
----------------------------------
Resolution: Fixed
Thanks Ilan for catching this. I fixed this in the trunk and into the 2.0 branch (see revision 398346).
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 me
thod localTearDown implemented in the JDO_Test superclass and it will open a new new pm instance.
> DeletePersistentFailsIfInstanceManagedBy
AnotherPersistenceManager - No cleanup for pm
> -------------------------------------------------------------------------------------
>
> Key: JDO-376
> URL: http://issues.apache.org/jira/browse/JDO-376
> Project: JDO
> Type: Bug
> Components: tck20
> Versions: JDO 2 rc1
> Reporter: Ilan Kirsh
> Assignee: Michael Bouschen
> Priority: Minor
> Fix For: JDO 2 final
>
> In org.apache.jdo.tck.api.persistencemanager. DeletePersistentFailsIfInstanceManagedBy
AnotherPersistenceManager, 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.jd
o.tck.query.api.Close after DeletePersistentFailsIfInstanceManagedBy
AnotherPersistenceManager fails, because the old PCPoint instances are still there.
--
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
|