Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Mon, 30 Jan 2012 18:30:10 +0000 (UTC)
From: "Brad Koehn (Updated) (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: 
 <1288227074.8323.1327948210124.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <857902575.8286.1327947850492.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (POOL-211) Proxy support for pooled objects
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brad Koehn updated POOL-211:
----------------------------

    Attachment: test.jar
                src.jar

Source code and tests. 
                
> 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
>            Reporter: Brad Koehn
>              Labels: features, patch
>             Fix For: Nightly Builds
>
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira