cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (Assigned) (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CXF-4180) LogUtils should default to CXF's Slf4jLogger if it can't find Log4J or JCL driver
Date Tue, 20 Mar 2012 07:59:44 GMT

     [ https://issues.apache.org/jira/browse/CXF-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Willem Jiang reassigned CXF-4180:
---------------------------------

    Assignee: Daniel Kulp  (was: Willem Jiang)

Dan already commit a patch into to the trunk.

As this feature break the compatibility, we don't back port the patch to other branches.
                
> LogUtils should default to CXF's Slf4jLogger if it can't find Log4J or JCL driver
> ---------------------------------------------------------------------------------
>
>                 Key: CXF-4180
>                 URL: https://issues.apache.org/jira/browse/CXF-4180
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.5.2
>         Environment: Any
>            Reporter: Matt Bishop
>            Assignee: Daniel Kulp
>
> LogUtils looks for an instance of SLF4J's ILoggerFactory, then tests it's name for Log4J
and JUL. If it fails, it just bails out.
> Nicer would be to instead use the existing org.apache.cxf.common.logging.Slf4jLogger
in that case. This would keep us from having to use the silly META-INF/cxf/org.apache.cxf.Logger
configuration to set up Logback or another ILoggerFactory implementation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message