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 19:40:39 GMT
    [ http://issues.apache.org/jira/browse/JDO-335?page=comments#action_12370020 ] 

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

I think it is ok to avoid closing the PMF until the end of the configuration. Each setUp and
tearDown in the tests cleans up the persistent instances in the datastore.

If the JDO implementation is doing caching in the PMF, then the caching must not affect the
results of running the TCK. 

Do you know that there is a specific issue with caching that can be explained in some more
detail? 

> 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