[
https://issues.apache.org/jira/browse/CXF-9096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko resolved CXF-9096.
-------------------------------
Resolution: Duplicate
> cxf-core LogUtils unable to static init loggerClass when slf4j v2 is used
> --------------------------------------------------------------------------
>
> Key: CXF-9096
> URL: https://issues.apache.org/jira/browse/CXF-9096
> Project: CXF
> Issue Type: Bug
> Affects Versions: 4.1.0, 3.5.10, 3.6.5, 4.0.6
> Reporter: Dmytro Sylaiev
> Priority: Major
>
> When running cxf code, LogUtils initialize the logger class and when there's
> no explicit specification, it loads the Slf4j StaticLoggerBinder
> [https://github.com/apache/cxf/blob/main/core/src/main/java/org/apache/cxf/common/logging/LogUtils.java#L101]
> to check if slf4j is in classpath and then initialize
> org.slf4j.LoggerFactory::getILoggerFactory
>
> The problem is that for slf4j-api v2 the StaticLoggerBinder class was removed
> and when we use CXF with slf4j v2 it doesn't set any value to the loggerClass
> field out of the box, so user need to either call setLoggerClass method or
> set the "org.apache.cxf.Logger" system property/resource.
>
> Is it expected behavior?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
