[jira] Updated: (POOL-169) POOL 2.0 suggested deprecations - deprecate direct access to protected fields, make factories immutable

["Phil Steitz (JIRA)" <ji...@apache.org>]

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

Phil Steitz updated POOL-169:
-----------------------------

    Summary: POOL 2.0 suggested deprecations - deprecate direct access to protected fields, make factories immutable  (was: POOL 2.0 suggested deprecations)

> POOL 2.0 suggested deprecations - deprecate direct access to protected fields, make factories immutable
> -------------------------------------------------------------------------------------------------------
>
>                 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.
> 6. Pool factories should be immutable - i.e., setFactory methods should be deprecated in pool implementations

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.