|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
LogIF | The interface that any 3rd party logging system adapter must implement. |
Trace | Used within the logging system to "trace" method invocation on a specific thread by decorating logging messages with a "trace category". |
Class Summary | |
ConsoleImpl | Display logging information to the System.out stream. |
ConsoleImpl.Test | |
MessageLog | This class provides an abstraction to any logging system. |
Introduction
The logging package was created to maintain a buffer between ObjectWave
code and third party dependencies. By using the logging package,
code created is not tied to any one logging implementation. Implementations
can be "plugged-in". Examples of different plugins might be Apache's Log4J
logging system, or perhaps a Unix like syslog plugin.
Custom logging implementations are accessed via the adapter pattern which
requires custom implementations to provide a LogIF adapter class. This
adapter is then set as the LoggingEngine in the MessageLog class via the
setLoggingEngine(LogIf) method.
MessageLog
The message log class is the main entry point into the logging package for
client code. This should be the only class required to perform any of
your logging needs. See the API for details.
Current LogIF implementations
com.objectwave.logging.ConsoleImpl - This
implementation simply logs to stdout.
com.objectwave.logging.log4j.Log4jImpl - This
is the adapter which connects the logging system to the Apache Log4j
logging system.
|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |