[
https://issues.apache.org/jira/browse/POOL-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883070#action_12883070
]
Phil Steitz commented on POOL-169:
----------------------------------
Note that items 1-4 above refer to previously unreleased classes. Therefore
there is no deprecation action required to implement these changes in the 2.0
branch. We should separately discuss whether we want to keep the composite
package for 2.0.
> 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.
