Content deleted Content added
Line 3:
==Functionality Overview==
Logging a message is broken into three major pieces:the Logger, Formatter and the Appender (Handler). The Logger is responsible for capturing the message to be logger, along with certain meta-data like level, and passing that to the logging framework. After receiving the message, the logging framework calls the Formatter on the message. The Formatter accepts and object and formats it for proper logging. The logging framework then hands the formatted message to the appropriate Appender to dispostion of the message. This might include displaying on a console, writing to disk, appending to a database, or notification via email.
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.
Line 47 ⟶ 50:
* write to a listening socket
* bit-bucket (/dev/null)
==Best Practices==
==Comparing Features==
| |||