Java logging framework: Difference between revisions

Revision as of 06:34, 23 May 2006

Revision as of 22:02, 11 June 2006

Line 1:

==Introduction of Java Logging Frameworks==

[[data logging|Logging]] is a common issue for most development teams. There have been several frameworks developed to ease and standardize the process of logging for the [[Java platform|Java platform]]. This page covers general purpose logging frameworks. There are other logging frameworks, toolkits and libraries like [http://aopclsuite.sourceforge.net/tracing.html Tracing Class Loader] but that is for another topic.

==Functionality Overview==

Line 6:

Simpler logging frameworks, like Java Logging Framework by the Object Guy, combine the logger and the appender together. This makes for simple initial configuration, but less configurable, especially as the project is moved across environments.

===Logger===

Most frameworks support a the notion of a Logger. A Logger is an object that allows the application to log data without regard to where the data is actually logged. The application logs a message in the form of an object or and object and and exception. When a Logger is created, it is given a name or an identifier. When logging a message, it is logged at a certain level or priority.

====Name====

A logger has a name. The name is usually hierarchical, with periods (.) separating the levels. A common naming scheme is to use the name of the class or package that is doing the loggings. Both log4j and the Java API supported defining Handlers higher up the hierarchy.