blocks|key|2005345|text|这个问题似乎与354837相同。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2005346|简单的答案是，如果您正在编写一个库，而这个库可能被丢弃到无法控制日志记录的应用程序中，那么您就会选择Commons，如果不是，这是另一个选择。我个人在所有情况下都使用CL，原因很简单--我不需要记住框架之间的差异。|2005347|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/354837/whats-up-with-logging-in-java^0|7|6|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

This question seems identical to <a href="https://stackoverflow.com/questions/354837/whats-up-with-logging-in-java">354837</a>.

The simple answer is that you'd go for Commons Logging if you're writing a library that may be dropped into applications where you have no control over the logging, one of the other choices if not. I personally use CL in all cases, simply because it's common -- I don't need to remember the differences between frameworks.

blocks|key|769780|text|Commons是奇怪类加载问题的来源。如果你可以的话，尽量避免。在开发应用程序时，我更喜欢log4j。如果您开发库/框架，并且不想强制执行日志库，请选择slf4j。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|769781|entityMap|0|LINK|mutability|MUTABLE|url|http://www.qos.ch/logging/classloader.jsp^0|8|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Commons Logging is <a href="http://www.qos.ch/logging/classloader.jsp" rel="nofollow noreferrer">source of strange classloading problems</a>. Avoid it if you can. I prefer log4j when developing application. If you develop library/framework and you don't want to enforce logging library, choose slf4j.

blocks|key|2005390|text|无论官方职位是"log4j“，都是标准的日志记录框架。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2005391|它工作得很好，而且已经存在了一段时间。它是成千上万个应用程序和软件包使用的部署最多的日志框架。它也是最有可能出现在开发人员简历上的日志框架。|2005392|坚持使用log4j，没有什么好的理由去尝试其他的东西。|2005393|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Whatever the official position is "log4j" is the standard logging framework.

It works well and has been around for a while. Its the most deployed logging framework used by thousands of apps and packages. Its also the logging framework most likely to appear on a developers CV.

Stick with log4j there is no good reason to try anything else.

blocks|key|2005413|text|如果是它的新代码，我将从slf4j开始，因为它提供了在底层日志api之间切换的最简单方法，只需在应用程序的类中包含所需的slf4j_api.jar。例如，如果您从log4j开始，仍然必须在log4j.xml中配置一个Conole记录器以查看日志输出，使用slf4j，只需包含slf4j-simple.jar。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2005414|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If its new code i'd start with slf4j, since it provides the simplest way to switch between the underlying logging api's by just including the required slf-[logging_api].jar in the classparth of your app. For example - if you start with log4j you still have to configure a Conole logger in a log4j.xml to see your logging output, with slf4j you just include the slf4j-simple.jar.

blocks|key|472320|text|Logback是对log4j的重写。如果您喜欢log4j，您应该更喜欢logback。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|472321|此外，logback是SLF4J+API的一个本机实现，这意味着您正在使用logback，而实际上您正在使用SLF4J。因此，如果出于任何原因，您希望切换回另一个日志框架，无论是log4j还是j.u.l。您可以通过将一个jar文件替换为另一个jar文件来做到这一点。|472322|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Logback is a rewrite of log4j. If you like log4j, you should like logback even better.

Moreover, logback is a native implementation of the SLF4J API which means that is you are using logback, then you are actually using SLF4J. Thus, if for any reason you wish to switch back to another logging framework, be it log4j or j.u.l. you can do so by replacing one jar file with another.

Java has a lot of frameworks / APIs that help you do logging in your application:

<ol>
<li>The Java API has java.util.logging package.</li>
<li>Apache's Log4j.</li>
<li>Apache's Commons Logging.</li>
<li>SLF4J (logging Facade).</li>
<li>jLo.
and many many more...</li>
</ol>

I've always used the log4j library, i found it sufficient most of the time, and extensible when i needed more control. 

Anyone who had experience with more than one framework can share his experience? when is it better to use one framework over the other and from application architecture point of view? Why would i prefer one over other?

Thanks

Find a way in the java logging frameworks scene

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

Java有许多帮助您在应用程序中进行日志记录的框架/API：Java有java.util.logging包。阿帕奇的Log4j。阿帕奇的共用日志。SLF4J (日志门面)。jLo。还有更多的..。我一直使用log4j库，我发现它大部分时间都足够了，并且在需要更多的控制时是可扩展的。任何有多个框架经验的人都可以分享他的经...

问在java日志框架场景中找到一种方法
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在java日志框架场景中找到一种方法EN