You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Rick Curtis (JIRA)" <ji...@apache.org> on 2014/02/05 23:50:10 UTC

[jira] [Resolved] (OPENJPA-2135) Deprecate prepareForPooling

     [ https://issues.apache.org/jira/browse/OPENJPA-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Curtis resolved OPENJPA-2135.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4.0

Committed revision 1564976 to trunk.

> Deprecate prepareForPooling
> ---------------------------
>
>                 Key: OPENJPA-2135
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2135
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: jdbc, performance
>    Affects Versions: 2.2.1, 2.3.0
>            Reporter: Kevin Sutter
>            Assignee: Rick Curtis
>             Fix For: 2.4.0
>
>
> Now that we have determined that closing Connections was overkill during the prepareForPooling processing when ConnectionRetainMode is set to "always" (OPENJPA-2134), maybe it's time to kill the whole idea of prepareForPooling.  If application servers are doing their job correctly, all that should be necessary is to call clear() on the EntityManager before pooling an EM.  Instead of removing this public API immediately, I'm thinking we should mark it as deprecated (just in case any app servers are still dependent on this processing).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)