db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-335) Close PMF after running each configuration
Date Sat, 11 Mar 2006 20:18:40 GMT
    [ http://issues.apache.org/jira/browse/JDO-335?page=comments#action_12370026 ] 

Craig Russell commented on JDO-335:
-----------------------------------

Perhaps we can add a flag jdo.tck.closePMFAfterEachTest that defaults to false for the TCK
runs. Then you can debug your implementation with the flag set to true and the TCK can run
faster for the normal case.

> 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


Mime
View raw message