[ http://issues.apache.org/jira/browse/IBATIS-305?page=all ]
Jeff Butler closed IBATIS-305:
------------------------------
Fix Version: 2.2.0
Resolution: Fixed
I corrected and expanded the documentation to reflect how iBATIS actually uses
logging (for example, iBATIS is no longer dependant on Jakarta Commons
Logging). I also added two methods to the LogFactory class that can be used to
select specific log implementations if you want to override the default search
order.
> 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
> Assignee: Jeff Butler
> Priority: Minor
> Fix For: 2.2.0
>
> 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
