We already posted the Junit test. It is the second attachment we put in the
bug.
- Original Message -
From: Dirk Verbeeck [EMAIL PROTECTED]
To: Jakarta Commons Developers List [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, August 03, 2004 7:48 PM
Subject: [DBCP] Bug 30426 - need
Can you check again, because I don't see it.
-- Dirk
David Rosenstark wrote:
We already posted the Junit test. It is the second attachment we put in the
bug.
- Original Message -
From: Dirk Verbeeck [EMAIL PROTECTED]
To: Jakarta Commons Developers List [EMAIL PROTECTED]
Cc: [EMAIL
Message-
From: Waldhoff, Rodney [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 01, 2002 12:25 PM
To: 'Jakarta Commons Developers List'
Subject: RE: [POOL] Bug
This could easily be done by doing a contains()
check on the collection that backs the pool before
adding the object
GenericObjectPool with this behavior.
-Original Message-
From: Waldhoff, Rodney [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 01, 2002 12:25 PM
To: 'Jakarta Commons Developers List'
Subject: RE: [POOL] Bug
This could easily be done by doing a contains()
check on the collection that backs
This could easily be done by doing a contains()
check on the collection that backs the pool before
adding the object to it.
If and only if the equality method identifies unique instances of objects
within the pool.
You could implement a [Keyed]ObjectPool to do this, or perhaps better