[jboss-jira] [JBoss JIRA] Closed: (JBAS-6602) Log4jService should use the new JDKLevel class when setting log levels

Dimitris Andreadis (JIRA) jira-events at lists.jboss.org
Tue Mar 10 08:18:22 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBAS-6602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dimitris Andreadis closed JBAS-6602.
------------------------------------

    Resolution: Done


Done.

> Log4jService should use the new JDKLevel class when setting log levels
> ----------------------------------------------------------------------
>
>                 Key: JBAS-6602
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6602
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>            Reporter: Dimitris Andreadis
>            Assignee: Dimitris Andreadis
>             Fix For: JBossAS-5.1.0.Beta1, JBossAS-6.0.0.Alpha1
>
>
> This is to allow the dynamic setting of log levels through the setLoggerLevel(logger, level) method, that support the new org.jboss.logging.log4j.JDKLevel levels (i.e. SEVER, WARNING, CONFIG, FINE, FINER, FINEST).

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

        



More information about the jboss-jira mailing list