openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (OPENJPA-2135) Deprecate prepareForPooling
Date Wed, 05 Feb 2014 22:48:11 GMT

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

Rick Curtis reassigned OPENJPA-2135:
------------------------------------

    Assignee: Rick Curtis  (was: Kevin Sutter)

> 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
>
> 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)

Mime
View raw message