-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David,
On 4/1/2009 11:25 AM, David Smith wrote: > This is assuming the developer didn't unwrap any of the DBCP objects to > access driver specific features. In that case, the original wrapped > objects need to be maintained and closed instead of the unwrapped objects. I suppose that depends on what exactly you did. If all you did was unwrap a Statement object to do some BLOB operations or something, I would expect that you can safely ignore the fact that you unwrapped it. Actually, I can't think of a reason why you'd have to use the unwrapped version of the statement or result set (or even connection) to perform state management (i.e. calling close()). In fact, I would think taking such action would confuse the hell out of the connection pool and break lots of things. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknT1qAACgkQ9CaO5/Lv0PDlagCgjNWwDR8aHoJbPBzoEN5sm5pB +iAAn2HiHInywSn60x/u1h+s+OLPoucc =k0BQ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
