What is a logging framework,
and why do I need one?
Logging is the process of notifying some entity of a particular event. An entity
can be the system console, a file on disk, a database, or a remote computer, to
name a few. Events can be simple debug information for an application in development,
runtime exceptions for an application in a production environment, or a record of
actions taken by a user--such as visiting a web page.
A framework is a group of classes that form the foundation for a subset of functionality
in an application. Frameworks should be designed to be extendible, flexible, and
adaptable to the precise requirements of any given application. And, of course,
a good framework should be relatively easy to use.
Okay, so why do I need a logging framework?
Logging is important to all but the simplest of applications. You can choose to
write logging code throughout your application that doesn't provide the
flexibility and maintainability of a framework, or
write your own framework, or
use a quality framework that already exists.
I've looked at other frameworks. Why should I use this one?
Do you have a version of this framework for Java?
Who else uses a logging framework authored by The Object Guy?
Frameworks and tools authored by The Object Guy are currently being used in
numerous commercial applications, by independent software consultants, and by custom