You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Phil Steitz (JIRA)" <ji...@apache.org> on 2010/06/28 02:35:49 UTC
[jira] Commented: (POOL-169) POOL 2.0 suggested deprecations
[ https://issues.apache.org/jira/browse/POOL-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883005#action_12883005 ]
Phil Steitz commented on POOL-169:
----------------------------------
Item 5. has been implemented for StackKeyedObjectPoolFactory in r958436.
> POOL 2.0 suggested deprecations
> -------------------------------
>
> Key: POOL-169
> URL: https://issues.apache.org/jira/browse/POOL-169
> Project: Commons Pool
> Issue Type: Improvement
> Reporter: Sebb
> Fix For: 1.5.5
>
>
> This issue is intended to collect information on changes to Pool which will require deprecations and change of API.
> 1. Lender.setCompositeObjectPool should be deprecated, and implementations should be changed to include setup of the pool in their ctors.
> 2. composite.Manager.setCompositeObjectPool - ditto
> 3. composite.ActiveLimitManager.setMaxActive
> 4. CompositeObjectPool.setOwningCompositeKeyedObjectPool
> 5. Pool factories (GenericObjectPoolFactory, GenericKeyedObjectPoolFactory, StackObjectPoolFactory, StackKeyedObjectPoolFactory) should be made immutable in Pool 2.0. Getters should be added for configuration properties and protected fields should be deprecated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.