You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2013/10/14 12:53:43 UTC
[jira] [Resolved] (POOL-211) Proxy support for pooled objects
[ https://issues.apache.org/jira/browse/POOL-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Thomas resolved POOL-211.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0
This has been implemented. There is still some refactoring to do but the implementation is complete.
> Proxy support for pooled objects
> --------------------------------
>
> Key: POOL-211
> URL: https://issues.apache.org/jira/browse/POOL-211
> Project: Commons Pool
> Issue Type: Improvement
> Affects Versions: 1.6, 2.0
> Reporter: Brad Koehn
> Labels: features, patch
> Fix For: 2.0
>
> Attachments: src.jar, test.jar
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Attached are files and tests that would allow users of commons-pool to interact with a proxy to the pooled object rather than the pooled object itself. This provides two benefits: detection of leaked pooled objects (when returnObject() isn't called) with a stack trace and detection of using pooled objects after they have been returned to the pool. The system provides a delegate which can be placed in front of any ObjectPool, similar to calling Collections.unmodifiableCollection(). Callers do not know that they're working with a proxy rather than the pooled object itself. Implementations are provided to use Java proxies or CGLib (useful when the pooled object doesn't implement an interface). Unit tests are also provided.
--
This message was sent by Atlassian JIRA
(v6.1#6144)