Re: [DBCP] isClosed contract (DBCP-398)

2013-05-28 Thread Mark Thomas
On 27/05/2013 15:49, Phil Steitz wrote: We need to make a decision on whether or not to change the contract for PoolableConnection (or DelegatingConnection or PoolGuardWrapper) isClosed. There are two changes suggested in DBCP-398: 1) Currently, isClosed returns true if the connection

Re: [DBCP] isClosed contract (DBCP-398)

2013-05-28 Thread Phil Steitz
On 5/28/13 1:58 AM, Mark Thomas wrote: On 27/05/2013 15:49, Phil Steitz wrote: We need to make a decision on whether or not to change the contract for PoolableConnection (or DelegatingConnection or PoolGuardWrapper) isClosed. There are two changes suggested in DBCP-398: 1) Currently,

[DBCP] isClosed contract (DBCP-398)

2013-05-27 Thread Phil Steitz
We need to make a decision on whether or not to change the contract for PoolableConnection (or DelegatingConnection or PoolGuardWrapper) isClosed. There are two changes suggested in DBCP-398: 1) Currently, isClosed returns true if the connection handle has been closed by the client *or* the

Re: [DBCP] isClosed contract (DBCP-398)

2013-05-27 Thread Gary Gregory
On Mon, May 27, 2013 at 10:49 AM, Phil Steitz phil.ste...@gmail.com wrote: We need to make a decision on whether or not to change the contract for PoolableConnection (or DelegatingConnection or PoolGuardWrapper) isClosed. There are two changes suggested in DBCP-398: 1) Currently, isClosed