Home >> All >> org >> apache >> log4j >> [ spi Javadoc ]

• org.apache.log4j.spi: Javadoc index of package org.apache.log4j.spi.


Package Samples:

• org.apache.log4j.spi

Classes:

• Filter: Users should extend this class to implement customized logging event filtering. Note that org.apache.log4j.Category and org.apache.log4j.AppenderSkeleton , the parent class of all standard appenders, have built-in filtering rules. It is suggested that you first use and understand the built-in rules before rushing to write your own custom filters. This abstract class assumes and also imposes that filters be organized in a linear chain. The decide(LoggingEvent) 55 method of each filter is called sequentially, in the order of their addition to the chain. The decide(LoggingEvent) 55 method must return ...
• RepositorySelector: The LogManager uses one (and only one) RepositorySelector implementation to select the LoggerRepository for a particular application context. It is the responsability of the RepositorySelector implementation to track the application context. Log4j makes no assumptions about the application context or on its management. See also LogManager .
• TriggeringEventEvaluator: Implementions of this interface allow certain appenders to decide when to perform an appender specific action. For example the org.apache.log4j.net.SMTPAppender sends an email when the isTriggeringEvent(org.apache.log4j.spi.LoggingEvent) 55 method returns true and adds the event to an internal buffer when the returned result is false .
• ThrowableInformation: ThrowableInformation is log4j's internal representation of throwables. It essentially consists of a string array, called 'rep', where the first element, that is rep[0], represents the string representation of the throwable (i.e. the value you get when you do throwable.toString()) and subsequent elements correspond the stack trace with the top most entry of the stack corresponding to the second entry of the 'rep' array that is rep[1].
• RootLogger: RootLogger sits at the top of the logger hierachy. It is a regular logger except that it provides several guarantees. First, it cannot be assigned a null level. Second, since root logger cannot have a parent, the getChainedLevel() 55 method always returns the value of the level field without walking the hierarchy.
• ErrorHandler: Appenders may delegate their error handling to ErrorHandlers . Error handling is a particularly tedious to get right because by definition errors are hard to predict and to reproduce. Please take the time to contact the author in case you discover that errors are not properly handled. You are most welcome to suggest new error handling policies or criticize existing policies.
• LoggerRepository: A LoggerRepository is used to create and retrieve Loggers . The relation between loggers in a repository depends on the repository but typically loggers are arranged in a named hierarchy. In addition to the creational methods, a LoggerRepository can be queried for existing loggers, can act as a point of registry for events related to loggers.
• VectorWriter: VectorWriter is a seemingly trivial implemtantion of PrintWriter. The throwable instance that we are trying to represnt is asked to print itself to a VectorWriter. By our design choice, r string representation of the throwable does not contain any line separators. It follows that println() methods of VectorWriter ignore the 'ln' part.
• LoggingEvent: The internal representation of logging events. When an affirmative decision is made to log then a LoggingEvent instance is created. This instance is passed around to the different log4j components. This class is of concern to those wishing to extend log4j.
• LoggerFactory: Implement this interface to create new instances of Logger or a sub-class of Logger. See examples/subclass/MyLogger.java for an example.
• RootCategory: Replaced by RootLogger .
• HierarchyEventListener: Listen to events occuring within a Hierarchy .
• Configurator: Implemented by classes capable of configuring log4j using a URL.
• LocationInfo: The internal representation of caller location information.
• OptionHandler: A string based interface to configure package components.
• ErrorCode: This interface defines commonly encoutered error codes.
• AppenderAttachable: Interface for attaching appenders to objects.
• DefaultRepositorySelector
• RendererSupport
• NullWriter

Home | Contact Us | Privacy Policy | Terms of Service