[ 
http://issues.apache.org/jira/browse/IBATIS-305?page=comments#action_12415881 ] 

Jeff Butler commented on IBATIS-305:
------------------------------------

I do think we need to add some information to the documentation about logging.

Just to verify, you are seeing log statements on the "java.sql" classes, but 
not on the "com.ibatis" classes - right?

In truth, iBATIS does very little logging with the "com.ibatis" classes.  Most 
of the interesting log statements from iBATIS will be in the "java.sql" 
classes.  Maybe what you are seeing is the normal output from iBATIS logging.  
A good test would be to enable caching on some statement and see if there are 
log statements from "com.ibatis".  Caching is one of the very few places where 
iBATIS does log to the "com.ibatis" classes.


> Cannot get log output for com.ibatis classes
> --------------------------------------------
>
>          Key: IBATIS-305
>          URL: http://issues.apache.org/jira/browse/IBATIS-305
>      Project: iBatis for Java
>         Type: Bug

>  Environment: tomcat 5.5.* on windows
>     Reporter: Ben Munat
>     Priority: Minor

>
> After a conversation on the mailing list, I noticed that I don't get any log 
> statements for com.ibatis classes and don't remember ever seeing such on 
> several projects.
> I have a log4j.properties file like this:
> log4j.rootLogger=INFO, stdout
> log4j.logger.com.ibatis=DEBUG
> log4j.logger.java.sql=DEBUG
> #... etc.
> And I have the commons-logging.jar in the WEB-INF/lib of my build. I 
> discovered that I also had a commons-logging in tomcat's common/lib. Removing 
> that got rid of a double-logging problem that I had wondered about for a 
> while, but I still don't see any com.ibatis log output. 
> This isn't too big an issue for me, because I'm mostly interested in the sql 
> queries and I get those just fine having the java.sql logger. It is strange, 
> however, not to be able to get ibatis log output at all.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to