Ofcourse it is possible to add a second log4j category to handle the latter output, but that is somewhat overdone. Adding a "program logic marker" to highlight the logic output is an option.
But personally I'd feel for adding a "trace" level between info and debug, for showing program logic to get closer to the place where stuff goes wrong and then switch to debug.
INFO: show program configuration info, etc TRACE: show program logic and flow DEBUG: show logic explanation / reasoning
Tom
Jacob Kjome wrote:
Thanks,
It was nice of you to put that comparison together. However, did you have a particular point you were trying to make? There have been lots of discussions on the list about how many/few levels are appropriate. Have you perused those already? Do you have an opinion in regard to what levels Log4j should or should not have?
Jake
At 02:32 PM 10/18/2003 -0700, you wrote:
Logging levels
Jakarta Log4j 1.2.8 ===================
http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/Level.html
class: org.apache.log4j.Level
FATAL ERROR WARN INFO DEBUG
JBoss 3.2.2 ===========
http://www.jboss.org/
class: org.jboss.logging.XLevel (extends org.apache.log4j.Level)
FATAL ERROR WARN INFO DEBUG TRACE
BEA Weblogic Server 8.1 =======================
http://edocs.bea.com/wls/docs81/javadocs/weblogic/logging/Severities.html
class: weblogic.logging.Severities
ALERT CRITICAL DEBUG EMERGENCY ERROR INFO NOTICE WARNING
http://edocs.bea.com/wls/docs81/javadocs/weblogic/logging/WLLevel.html
class: weblogic.logging.WLLevel (extends java.util.logging.Level)
ALERT CRITICAL DEBUG EMERGENCY ERROR INFO NOTICE WARNING
Jakarta Commons Logging 1.0.3 =============================
http://jakarta.apache.org/commons/logging/apidocs/index.html
fatal error warn info debug trace
Apache Geronimo ===============
http://incubator.apache.org/projects/geronimo.html
class: org.apache.geronimo.common.log.log4j.XLevel (extends org.apache.log4j.Level)
FATAL ERROR WARN INFO DEBUG TRACE
java.util.logging (J2SE 1.4.2) ===============================
http://java.sun.com/j2se/1.4.2/docs/api/java/util/logging/Level.html
class: java.util.logging.Level
SEVERE WARNING INFO CONFIG FINE FINER FINEST
Avalon LogKit 1.2 =================
http://avalon.apache.org/logkit/api/org/apache/log/Priority.html
class: org.apache.log.Priority
FATAL_ERROR ERROR WARN INFO DEBUG
Jakarta Slide 1.0.16 ====================
http://jakarta.apache.org/slide/javadoc/org/apache/slide/util/logger/Logger.
html
interface: org.apache.slide.util.logger.Logger
EMERGENCY CRITICAL ERROR WARNING INFO DEBUG
Acelet SuperLogging ===================
http://acelet.com/super/help/api/com/acelet/logging/Logging.html
SEVERE WARNING INFO CONFIG FINE FINER FINEST
ObjectGuy Java Logging Framework ================================
http://www.theobjectguy.com/javalog/
debug info status warning error critical fatal
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
