You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Matt Bishop (Created) (JIRA)" <ji...@apache.org> on 2012/03/14 01:06:42 UTC
[jira] [Created] (CXF-4180) LogUtils should default to CXF's
Slf4jLogger if it can't find Log4J or JCL driver
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
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
[jira] [Assigned] (CXF-4180) LogUtils should default to CXF's
Slf4jLogger if it can't find Log4J or JCL driver
Posted by "Willem Jiang (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CXF-4180:
---------------------------------
Assignee: Willem Jiang
> 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: Willem Jiang
>
> 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
[jira] [Resolved] (CXF-4180) LogUtils should default to CXF's
Slf4jLogger if it can't find Log4J or JCL driver
Posted by "Daniel Kulp (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-4180.
------------------------------
Resolution: Fixed
Fix Version/s: 2.6
> 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
> Fix For: 2.6
>
>
> 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
[jira] [Assigned] (CXF-4180) LogUtils should default to CXF's
Slf4jLogger if it can't find Log4J or JCL driver
Posted by "Willem Jiang (Assigned) (JIRA)" <ji...@apache.org>.
[ 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