[jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-39) JDK logging levels don't match our standard levels

[David Lloyd (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=comments#action_12384324 ] 
            
David Lloyd commented on JBCOMMON-39:
-------------------------------------

The problem is that if you use the JDK14LoggerPlugin, and you log a message at, say, TRACE, it shows up as FINER in the log.  And the DOMConfigurator for the JDK plugin has to map the "old" log4j names to the (roughly) equivalent JUL name.  I propose that we just create a subclass of java.util.logging.Level, and an instance for each of the log levels that WE use, e.g. TRACE, DEBUG, etc.  Then not only will the old, familiar levels be printed in the log, but then JUL will parse the log level names for us, so we don't need to map them.

No forum thread because honestly I don't know what forum is relevant for this project.

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira