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 "Christian Ernst (JIRA)" <ji...@apache.org> on 2006/03/11 14:02:53 UTC

[jira] Commented: (JDO-335) Close PMF after running each configuration

    [ http://issues.apache.org/jira/browse/JDO-335?page=comments#action_12369989 ] 

Christian Ernst commented on JDO-335:
-------------------------------------

>From my point of view we might must close even the PMF more often.
So removing from teardown is in my eyes a bad idea.
The reason is that we never now what kind of caching the JDO Implementation is doing
and only the closing of a PMF allows us to be sure that there is nothing cached.

> 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