Dashboard > iBATIS DataMapper > Home > Not Yet Documented > JDBC logging issues
JDBC logging issues
Added by Gwyn Evans, last edited by Gwyn Evans on Nov 13, 2007
Labels: 
(None)


There's an issue with logging of JDBC objects such that means that you won't see any JDBC logging if java.sql.Connection logging isn't enabled.

To quote Jeff Butler:

This is related to a structural defect in the way iBATIS does logging. iBATIS does logging through dynamic proxies for all the JDBC objects - and these objects are only proxied if the Connection object itself is proxied. The Connection object is proxied only if debugging is enabled for it. So, you'll not get any logging unless debugging is enabled for Connection.

Seen in 2.3.0 (and previous)


Site running on a free Atlassian Confluence Open Source Project License granted to OSS. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.5 Build:#811 Jul 25, 2007) - Bug/feature request - Contact Administrators