commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxx (JIRA)" <j...@apache.org>
Subject [jira] Created: (LOGGING-120) Support kinf of isPriorityEnabled / log(Priority) on org.apache.commons.logging.Logger
Date Wed, 05 Mar 2008 15:49:40 GMT
Support kinf of isPriorityEnabled / log(Priority) on org.apache.commons.logging.Logger
--------------------------------------------------------------------------------------

                 Key: LOGGING-120
                 URL: https://issues.apache.org/jira/browse/LOGGING-120
             Project: Commons Logging
          Issue Type: Improvement
    Affects Versions: 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.1, 1.0
            Reporter: Maxx
             Fix For: Nightly Builds, 2.0


Related to what's be done in library LogKit in class org.apache.log.Logger
 - check http://excalibur.apache.org/apidocs/org/apache/log/Logger.html#isPriorityEnabled(org.apache.log.Priority)
(former log tool in Apache Excalibur...)

... as well as what's available in library Log4j in class org.apache.log4j.Logger (extending
by org.apache.log4j.Category)
 - check http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Category.html#isEnabledFor(org.apache.log4j.Priority)

Would it be possible to support a kind of priority-level test method which support a Priority
as a param??

Same thing for log(Priority, message)
- check http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Category.html#log(org.apache.log4j.Priority,%20java.lang.Object)


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message