使用 SLF4J 发送/重定向/路由 java.util.logging.Logger (JUL) 到 Logback？

发布于 2024-11-07 09:42:40 字数 281 浏览 1 评论 0原文

是否可以对 java.util.logging.Logger 进行典型调用并使用 SLF4J 将其路由到 Logback？这会很好，因为我不必逐行重构旧的 jul 代码。

EG，假设我们有这一行：

private static Logger logger = Logger.getLogger(MahClass.class.getName());
//...
logger.info("blah blah blah");

将其配置为通过 SLF4J 调用会很好。

原文

Is it possible to have a typical call to java.util.logging.Logger and have it route to Logback using SLF4J? This would be nice since I wouldn't have to refactor the old jul code line by line.

EG, say we have this line:

private static Logger logger = Logger.getLogger(MahClass.class.getName());
//...
logger.info("blah blah blah");

It would be nice to configure this to call through SLF4J.

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

聚集的泪 2024-11-14 09:42:40

这非常简单，不再是性能问题。

SLF4J 手册中记录了两种方法。 Javadocs 中也有精确的示例

添加 jul-to- slf4j.jar 到您的类路径。或者通过 Maven 依赖项：

<dependency>
    <groupId>org.slf4j</groupId>
     <artifactId>jul-to-slf4j</artifactId>
    <version>1.7.0</version>
</dependency>

如果您没有logging.properties（对于java.util.logging），请将其添加到您的引导代码中：

SLF4JBridgeHandler.removeHandlersForRootLogger();
SLF4JBridgeHandler.install();

如果您有logging.properties（并且想要保留它），请将其添加到

handlers = org.slf4j.bridge.SLF4JBridgeHandler

其中：为了避免性能损失，请将此 contextListener 添加到 logback.xml （从 logback 版本 0.9.25 开始）：

<?xml version="1.0" encoding="UTF-8"?>
<configuration>

    <contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator">
        <!-- reset all previous level configurations of all j.u.l. loggers -->
        <resetJUL>true</resetJUL>
    </contextListener> 

    ...

</configuration>

It's very easy and not a performance issue anymore.

There are two ways documented in the SLF4J manual. There are also precise examples in the Javadocs

Add jul-to-slf4j.jar to your classpath. Or through maven dependency:

<dependency>
    <groupId>org.slf4j</groupId>
     <artifactId>jul-to-slf4j</artifactId>
    <version>1.7.0</version>
</dependency>

If you don't have logging.properties (for java.util.logging), add this to your bootstrap code:

SLF4JBridgeHandler.removeHandlersForRootLogger();
SLF4JBridgeHandler.install();

If you have logging.properties (and want to keep it), add this to it:

handlers = org.slf4j.bridge.SLF4JBridgeHandler

In order to avoid performance penalty, add this contextListener to logback.xml (as of logback version 0.9.25):

<?xml version="1.0" encoding="UTF-8"?>
<configuration>

    <contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator">
        <!-- reset all previous level configurations of all j.u.l. loggers -->
        <resetJUL>true</resetJUL>
    </contextListener> 

    ...

</configuration>

回复收藏 0 原文

~没有更多了~