Log4j Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 8: Line 8:


[[#Category|Category]] deprecation note: Logger is a subclass of [[#Category|Category]] and extends it. [[#Category|Category]] has been deprecated. Internally, whenever log4j is asked to produce a Category object, it will instead produce a Logger object. In order to preserve backward compatibility, methods that previously accepted category objects still continue to accept category objects.
[[#Category|Category]] deprecation note: Logger is a subclass of [[#Category|Category]] and extends it. [[#Category|Category]] has been deprecated. Internally, whenever log4j is asked to produce a Category object, it will instead produce a Logger object. In order to preserve backward compatibility, methods that previously accepted category objects still continue to accept category objects.
==Creating a Logger Instance==
The recommended way to create Logger instance is to request them by name from the LogManager:
<pre>
Logger log = LogManager.getLogger("some-name");
</pre>


=Log Levels=
=Log Levels=

Revision as of 00:02, 8 August 2016

Internal

Logger

Logger is the central class in the log4j package. Most logging operations, except configuration, are done through this class.

Category deprecation note: Logger is a subclass of Category and extends it. Category has been deprecated. Internally, whenever log4j is asked to produce a Category object, it will instead produce a Logger object. In order to preserve backward compatibility, methods that previously accepted category objects still continue to accept category objects.

Creating a Logger Instance

The recommended way to create Logger instance is to request them by name from the LogManager:

Logger log = LogManager.getLogger("some-name");

Log Levels

Category

This class has been deprecated and replaced with the Logger subclass. There is no need for new client code to use or refer to the Category class.