Package com.vignette.portal.log

Provides configurable logging of status, warning, error, and debugging messages for one or more subsystems.

See:
Package Summary

Interface Summary

LogContext

Many applications will want peices of context included in every log call, or every call of a particular level or above.

Class Summary

Log	Logging is the process of reporting useful information to the end user or administrator of a particular application.
LogConfiguration	Contains the methods used to configure logging.
LogSubsystemInfo
LogWrapper	You can use this wrapper to make logging easier.

Exception Summary

LogException
NotSupportedException

Package com.vignette.portal.log Description

Provides configurable logging of status, warning, error, and debugging messages for one or more subsystems. The framework for this API is the Apache Jakarta Log4j Project, which supports multiple log output destinations as well as log filtering based on hierarchical namespacing. A namespace can correspond to a package name, or it can provide a cross-package view of the system. For example, if logging were turned on for the com.vignette.portal namespace, the log output would include messages for that package and all of its subpackages. In addition, a security namespace could be created to log failed authorization attempts and other security-related events across the system.

This API replaces the functionality provided by com.epicentric.common.LogConstants, com.epicentric.common.LogInterface, com.epicentric.common.Log, and com.epicentric.common.FileLog, which have been deprecated.

Logging configuration is controlled through the portal properties.txt file and the log4j.properties file. Settings in log4j.properties override those in properties.txt.

For details about the Log4j Project, see http://jakarta.apache.org/log4j/docs/index.html. In particular, the org.apache.log4j.PropertyConfigurator class controls how Log4j works with an external configuration file.

See:
Discussion
Code Example