On Aug 19, 2010, at 6:43 PM, Chris Poulsen wrote: > the strategy I found to be least intrusive was to wrap the JDBC > connection/statements in my own Connection/*Statement classes and let > statements register themselves somewhere accessible from other threads on > creation and unregister on .close() before delegating to the inner instance.
Yeah, much better approach than overriding queries that I suggested. IIRC common-dbcp DataSource does that type of wrapping. No idea if any of that is extendable / customizable. Andrus
