commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy McArthur" <sandy...@apache.org>
Subject Re: [pool] BaseObjectPool.isClosed() visibility [was: Announcing Release Candidate 2 for Pool 1.3]
Date Fri, 24 Mar 2006 04:09:50 GMT
On 3/23/06, Gary Gregory <ggregory@seagullsoftware.com> wrote:
> This build works fine with our application.
>
> My only wish would be to make BaseObjectPool.isClosed() public.

Gary, are you really wanting a way to test if the pool is closed or do
you want the returnObject and invalidateObject methods to be more
graceful and accept objects borrowed from before the pool was closed?

The code in the trunk for pool 2 only throws IllegalStateExceptions
for the addObject and the borrowObject methods after close has been
called. The other methods will still seem to function normally but
really they are in a shutdown mode and just dispose of returned
objects.

--
Sandy McArthur

"He who dares not offend cannot be honest."
- Thomas Paine

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message