commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Waldhoff, Rodney" <rwald...@us.britannica.com>
Subject RE: [DBCP] : DelegatingConnection/PoolableConnection Bug ?
Date Tue, 02 Apr 2002 21:32:16 GMT
Can't say that I use Connection.isClosed often if at all, nor that I fully
understand the use cases here.

Technically speaking, if the underlying connection isn't closed, then
PoolableConnection still has an open channel to the database.  Does that
mean isClosed should return true?

I think you're suggesting that PoolableConnection.isClosed should return
true when the connection is in the pool, false when it's out of the pool
(and the underlying connection isn't closed either).  Sounds reasonable to
me.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message