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 "Michael Bouschen (JIRA)" <ji...@apache.org> on 2006/03/11 13:50:44 UTC
[jira] Updated: (JDO-335) Close PMF after running each
configuration
[ http://issues.apache.org/jira/browse/JDO-335?page=all ]
Michael Bouschen updated JDO-335:
---------------------------------
Attachment: JDO-335.patch
Attached you find a patch (JDO-335.patch) for review. It makes method JDO_Test.closePMF static, such that it can be called from BatchTestRunner. It also removes the call of closePMF from tearDown.
> Close PMF after running each configuration
> ------------------------------------------
>
> Key: JDO-335
> URL: http://issues.apache.org/jira/browse/JDO-335
> Project: JDO
> Type: Improvement
> Components: tck20
> Versions: JDO 2 rc1
> Reporter: Michael Bouschen
> Assignee: Michael Bouschen
> Priority: Minor
> Fix For: JDO 2 final
> Attachments: JDO-335.patch
>
> Today method tearDown (that is run at the end of each test method) closes the pmf.
> The proposal is to keep the pmf open for the next test method and close it at the end of running a configuration. That would allow to reuse resources bound to the pmf in multiple test cases.
--
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