Home >> All >> java >> util >> [ logging Javadoc ]

• java.util.logging: Javadoc index of package java.util.logging.


Package Samples:

• java.util.logging

Classes:

• FileHandler: A FileHandler publishes log records to a set of log files. A maximum file size can be specified; as soon as a log file reaches the size limit, it is closed and the next file in the set is taken. Configuration: Values of the subsequent LogManager properties are taken into consideration when a FileHandler is initialized. If a property is not defined, or if it has an invalid value, a default is taken without an exception being thrown. java.util.FileHandler.level - specifies the initial severity level threshold. Default value: Level.ALL . java.util.FileHandler.filter - specifies the name of a Filter ...
• LogManager: The LogManager maintains a hierarchical namespace of Logger objects and manages properties for configuring the logging framework. There exists only one single LogManager per virtual machine. This instance can be retrieved using the static method getLogManager() 55 . Configuration Process: The global LogManager object is created and configured when the class java.util.logging.LogManager is initialized. The configuration process includes the subsequent steps: If the system property java.util.logging.manager is set to the name of a subclass of java.util.logging.LogManager , an instance of that subclass ...
• SocketHandler: A SocketHandler publishes log records to a TCP/IP socket. Configuration: Values of the subsequent LogManager properties are taken into consideration when a SocketHandler is initialized. If a property is not defined, or if it has an invalid value, a default is taken without an exception being thrown. java.util.SocketHandler.level - specifies the initial severity level threshold. Default value: Level.ALL . java.util.SocketHandler.filter - specifies the name of a Filter class. Default value: No Filter. java.util.SocketHandler.formatter - specifies the name of a Formatter class. Default value: java.util.logging.XMLFormatter ...
• MemoryHandler: A MemoryHandler maintains a circular buffer of log records. Configuration: Values of the subsequent LogManager properties are taken into consideration when a MemoryHandler is initialized. If a property is not defined, or if it has an invalid value, a default is taken without an exception being thrown. java.util.MemoryHandler.level - specifies the initial severity level threshold. Default value: Level.ALL . java.util.MemoryHandler.filter - specifies the name of a Filter class. Default value: No Filter. java.util.MemoryHandler.size - specifies the maximum number of log records that are kept in the ...
• Logger: A Logger is used for logging information about events. Usually, there is a seprate logger for each subsystem or component, although there is a shared instance for components that make only occasional use of the logging framework. It is common to name a logger after the name of a corresponding Java package. Loggers are organized into a hierarchical namespace; for example, the logger "org.gnu.foo" is the parent of logger "org.gnu.foo.bar" . A logger for a named subsystem can be obtained through getLogger(java.lang.String) 55 . However, only code which has been granted the permission to control the ...
• ConsoleHandler: A ConsoleHandler publishes log records to System.err . Configuration: Values of the subsequent LogManager properties are taken into consideration when a ConsoleHandler is initialized. If a property is not defined, or if it has an invalid value, a default is taken without an exception being thrown. java.util.logging.ConsoleHandler.level - specifies the initial severity level threshold. Default value: Level.INFO . java.util.logging.ConsoleHandler.filter - specifies the name of a Filter class. Default value: No Filter. java.util.logging.ConsoleHandler.formatter - specifies the name of a Formatter ...
• Handler: A Handler publishes LogRecords to a sink, for example a file, the console or a network socket. There are different subclasses of Handler to deal with different kinds of sinks. FIXME: Are handlers thread-safe, or is the assumption that only loggers are, and a handler can belong only to one single logger? If the latter, should we enforce it? (Spec not clear). In any case, it needs documentation.
• Filter: By implementing the Filter interface, applications can control what is being logged based on arbitrary properties, not just the severity level. Both Handler and Logger allow to register Filters whose isLoggable method will be called when a LogRecord has passed the test based on the severity level.
• Level: A class for indicating logging levels. A number of commonly used levels is pre-defined (such as java.util.logging.Level.INFO ), and applications should utilize those whenever possible. For specialized purposes, however, applications can sub-class Level in order to define custom logging levels.
• LogRecord: A LogRecord contains the state for an individual event to be logged. As soon as a LogRecord instance has been handed over to the logging framework, applications should not manipulate it anymore.
• Formatter: A Formatter supports handlers by localizing message texts and by subsituting parameter values for their placeholders.
• StreamHandler: A StreamHandler publishes LogRecords to a instances of java.io.OutputStream .
• SimpleFormatter: A SimpleFormatter formats log records into short human-readable messages, typically one or two lines.
• ErrorManager: An ErrorManager deals with errors that a Handler encounters while logging.
• XMLFormatter: An XMLFormatter formats LogRecords into a standard XML format.
• LoggingPermission

Home | Contact Us | Privacy Policy | Terms of Service