You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2008/04/01 17:07:19 UTC

DO NOT REPLY [Bug 44727] New: Add missing Logger#isErrorEnabled and isWarningEnabled methods

https://issues.apache.org/bugzilla/show_bug.cgi?id=44727

           Summary: Add missing Logger#isErrorEnabled and isWarningEnabled
                    methods
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: ggregory@seagullsw.com


Created an attachment (id=21751)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=21751)
Missing methods and unit tests

Add missing isXyzEnabled methods:
- isErrorEnabled 
- isWarningEnabled 

Since 1.3 is dead, we had to port back from 1.3alpha7 to 1.2. But some of our
generated code calls isErrorEnabled which existed in 1.3.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

DO NOT REPLY [Bug 44727] Add missing Logger#isErrorEnabled and isWarningEnabled methods

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44727


Thorbjørn Ravn Andersen <th...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO




--- Comment #1 from Thorbjørn Ravn Andersen <th...@gmail.com>  2008-08-02 14:50:10 PST ---
I understand that the error and warn levels should be used so rarely that these
guard methods should not be necessary.

Personally I use the slf4j interface to log4j which give backend independence
and a simple way to avoid using these guards.  You might find
http://slf4j.org/faq.html#logging_performance interesting.

I suggest that this should be a WONTFIX


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org