Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.jboss.logging.appender.* (4)org.jboss.logging.layout.* (4)org.jboss.logging.util.* (5)

org.jboss.logging: Javadoc index of package org.jboss.logging.


Package Samples:

org.jboss.logging.layout: Common logging infrastructure.  
org.jboss.logging.util: Common logging infrastructure.  
org.jboss.logging.appender

Classes:

PatternLayout: A subclass of the log4j PatternLayout that add the following conversion characters: Conversion Character Effect z Used to output current thread NDC value. This can be used to obtain an NDC to augment any NDC associated with the LoggingEvent. This might be necessary if the LoggingEvent has been serialized between VMs. Z Used to output current thread MDC value. This can be used to obtain an MDC to augment any MDC associated with the LoggingEvent. This might be necessary if the LoggingEvent has been serialized between VMs. The Z conversion character must be followed by the key for the map placed between ...
PatternParserEx: A subclass of the log4j PatternParser that add the following conversion characters: Conversion Character Effect z Used to output current thread NDC value. This can be used to obtain an NDC to augment any NDC associated with the LoggingEvent. This might be necessary if the LoggingEvent has been serialized between VMs. Z Used to output current thread MDC value. This can be used to obtain an MDC to augment any MDC associated with the LoggingEvent. This might be necessary if the LoggingEvent has been serialized between VMs. The Z conversion character must be followed by the key for the map placed between ...
Log4jService: Initializes the Log4j logging framework. Supports XML and standard configuration file formats. Defaults to using 'log4j.xml' read from a system resource. Sets up a org.jboss.util.ThrowableListener to adapt unhandled throwables to a logger. Installs org.jboss.logging.util.LoggerStream adapters for System.out and System.err to catch and redirect calls to Log4j.
XLevel: Provides custom extention levels for use with the Log4j logging framework. Adds a trace level that is below the standard Log4j DEBUG level. This is a custom level that is 100 below the Priority.DEBUG_INT > Priority.DEBUG_INT 55 and represents a lower level useful for logging events that should only be displayed when deep debugging is required.
OnlyOnceErrorHandler: The OnlyOnceErrorHandler implements log4j's default error handling policy which consists of emitting a message for the first error in an appender and ignoring all following errors. The error message is printed on the specified print stream. This policy aims at protecting an otherwise working application from being flooded with error messages when logging fails.
Logger: Logger wrapper that tries to dynamically load a log4j class to determine if log4j is available in the VM. If it is the case, a log4j delegate is built and used. In the contrary, a null logger is used. This class cannot directly reference log4j classes otherwise the JVM will try to load it and make it fail. To set Only exposes the relevent factory and logging methods.
Log4jSocketServer: A Log4j SocketServer service. Listens for client connections on the specified port and creates a new thread and SocketNode to process the incoming client log messages. The LoggerRepository can be changed based on the clients address by using a custom LoggerRepositoryFactory. The default factory will simply return the current repository.
XPriority: Provides custom extention priorites for use with the Log4j logging framework. Adds a trace priority that is below the standard log4j DEBUG priority. This is a custom priority that is 100 below the Priority.DEBUG_INT and represents a lower priority useful for logging events that should only be displayed when deep debugging is required.
CategoryWriter: A subclass of PrintWriter that redirects its output to a log4j Category. This class is used to have something to give api methods that require a PrintWriter for logging. JBoss-owned classes of this nature generally ignore the PrintWriter and do their own log4j logging.
LoggerWriter: A subclass of PrintWriter that redirects its output to a log4j Logger. This class is used to have something to give api methods that require a PrintWriter for logging. JBoss-owned classes of this nature generally ignore the PrintWriter and do their own log4j logging.
CategoryStream: A subclass of PrintStream that redirects its output to a log4j Category. This class is used to map PrintStream/PrintWriter oriented logging onto the log4j Categories. Examples include capturing System.out/System.err
LoggerStream: A subclass of PrintStream that redirects its output to a log4j Logger. This class is used to map PrintStream/PrintWriter oriented logging onto the log4j Categories. Examples include capturing System.out/System.err
RegexEventEvaluator: An implementation of the log4j TriggeringEventEvaluator that matches the LoggingEvent message against the MDB{RegexEventEvaluator} regular expression.
LoggerPlugin: Defines a "pluggable" login module. In fact, this is only used to split between log4j and /dev/null. Choice is made in org.jboss.logging.Logger
NullLoggerPlugin: LoggerPlugin implementation producing no output at all. Used for client side logging when no log4j.jar is available on the classpath.
Log4jLoggerPlugin: Delegate for org.jboss.logging.Logger logging to log4j. Body of implementation mainly copied from old Logger implementation.
DailyRollingFileAppender: An extention of the default Log4j DailyRollingFileAppender which will make the directory structure for the set log file.
RollingFileAppender: An extention of the default Log4j RollingFileAppender which will make the directory structure for the set log file.
FileAppender: An extention of the default Log4j FileAppender which will make the directory structure for the set log file.
ThreadMDCConverter: A PatternConverter that uses the current thread MDC rather than the LoggingEvent MDC value.
ThreadNDCConverter: A PatternConverter that uses the current thread NDC rather than the LoggingEvent NDC value.

Home | Contact Us | Privacy Policy | Terms of Service