You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Clinton Begin (JIRA)" <ib...@incubator.apache.org> on 2005/03/01 17:41:51 UTC
[jira] Closed: (IBATIS-81) Change level for log4j.logger.com.ibatis...
[ http://issues.apache.org/jira/browse/IBATIS-81?page=history ]
Clinton Begin closed IBATIS-81:
-------------------------------
Assign To: Clinton Begin
Resolution: Invalid
The log level for these classes is set using "java.sql" packages. For example, java.sql.Connection will enable connection logging.
This was a concious decision made. It works as intended.
Cheers,
Clinton
> Change level for log4j.logger.com.ibatis...
> -------------------------------------------
>
> Key: IBATIS-81
> URL: http://issues.apache.org/jira/browse/IBATIS-81
> Project: iBatis for Java
> Type: Bug
> Components: Build/Deployment
> Versions: 2.0.8
> Environment: Windows 2000
> Sun Sparc 5.8, OS Sun Solaris 8
> Reporter: Martin Edlund
> Assignee: Clinton Begin
> Priority: Minor
>
> Changing the level for a logger through specifying a logger and its level in the log4j.properties file does not have affect on loggers in the package com.ibatis.common.jdbc.logging. I have tested both changing level for the package:
> com.ibatis.common.jdbc.logging
> and for these classes:
> com.ibatis.common.jdbc.logging.ConnectionLogProxy
> com.ibatis.common.jdbc.logging.PreparedStatementLogProxy
> com.ibatis.common.jdbc.logging.ResultSetLogProxy
> Changing levels for other loggers work, both when pointing out a package or a specific class, e.g:
> com.ibatis.common.jdbc
> com.ibatis.common.jdbc.SimpleDataSource
> The level is set to INFO so the code in the log4j.properties file is written like this:
> log4j.logger.com.ibatis.common.jdbc.SimpleDataSource=INFO
> log4j.logger.com.ibatis.common.jdbc.logging.PreparedStatementLogProxy=INFO
> log4j.logger.com.ibatis.common.jdbc.logging.ConnectionLogProxy=INFO
> log4j.logger.com.ibatis.common.jdbc.logging.ResultSetLogProxy=INFO
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira