Uses of Class org.apache.log4j.AppenderSkeleton

Overview

Package

Class

Use

Deprecated

Index

Home >> All >> org >> apache >> [ log4j overview ]

PREV NEXT

Uses of Class
org.apache.log4j.AppenderSkeleton

Uses of AppenderSkeleton in org.apache.log4j

Subclasses of AppenderSkeleton in org.apache.log4j

class AsyncAppender
          The AsyncAppender lets users log events asynchronously.

class CompositeRollingAppender
          CompositeRollingAppender combines RollingFileAppender and DailyRollingFileAppender
It can function as either or do both at the same time (making size based rolling files like RollingFileAppender until a data/time boundary is crossed at which time it rolls all of those files as per the DailyRollingFileAppender) based on the setting for rollingStyle.

To use CompositeRollingAppender to roll log files as they reach a certain size (like RollingFileAppender), set rollingStyle=1 (@see config.size)
To use CompositeRollingAppender to roll log files at certain time intervals (daily for example), set rollingStyle=2 and a datePattern (@see config.time)
To have CompositeRollingAppender roll log files at a certain size AND rename those according to time intervals, set rollingStyle=3 (@see config.composite)

class ConsoleAppender
          ConsoleAppender appends log events to System.out or System.err using a layout specified by the user.

class DailyFileAppender
          DailyFileAppender extends FileAppender to use filenames formatted with date/time information.

class DailyRollingFileAppender
          DailyRollingFileAppender extends FileAppender so that the underlying file is rolled over at a user chosen frequency.

class FileAppender
          FileAppender appends log events to a file.

class RollingFileAppender
          RollingFileAppender extends FileAppender to backup the log files when they reach a certain size.

class TempFileAppender
          TempFileAppender creates new unique file for each logging statement.

class WriterAppender
          WriterAppender appends log events to a java.io.Writer or an java.io.OutputStream depending on the user's choice.