The construction of the DelegatingConnection can/should moved up the call stack to the PoolablePreparedStatementStub or even to the PooledConnectionImpl.
(one DelegatingConnection for each PooledConnectionImpl)
There aren't any preparedstatementpool JUnit tests so I'm going to wait a little bit before commiting this fix. (It's not the simplest code ;-)
-- Dirk
Todd Carmichael wrote:
With this error in the code, translates to no coverage of this feature by
anyone. Statement pooling is a big part of improving scalability for our
application. I am surprised that no one else takes advantage of it.
ToddC
-----Original Message-----
From: Todd Carmichael [mailto:[EMAIL PROTECTED] Sent: Thursday, January 29, 2004 12:51 PM
To: '[EMAIL PROTECTED]'
Subject: RE: DO NOT REPLY [Bug 24136] - ClassCastException in DriverAdap
terCPDS when setPoolPreparedStatements(true)
Does anyone have a 'quick' fix for this problem? I have the code and can
make changes on my side.
Thanks!
ToddC
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
