Generated by
JDiff

java.util.logging Documentation Differences

This file contains all the changes in documentation in the package java.util.logging as colored differences. Deletions are shown like this, and additions are shown like this.
If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.
Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Class Level

The Level class defines a set of standard logging levels that can be used to control logging output. The logging Level objects are ordered and are specified by ordered integers. Enabling logging at a given level also enables logging at all higher levels.

Clients should normally use the predefined Level constants such as Level.SEVERE.

The levels in descending order are:

In addition there is a level OFF that can be used to turn off logging and a level ALL that can be used to enable logging of all messages.

It is possible for third parties to define additional logging levels by subclassing Level. In such cases subclasses should take care to chose unique integer level values and to ensure that they maintain the Object uniqueness property across serialization by defining a suitable readResolve method. @version 1.9 1210 02/0325/0102 @since 1.4

Class Level, Level ALL

ALL indicates that all messages should be logged. This level is initialized to Integer.MIN_VALUE.
Class Level, Level CONFIG

CONFIG is a message level for static configuration messages.

CONFIG messages are intended to provide a variety of static configuration information to assist in debugging problems that may be associated with particular configurations. For example CONFIG message might include the CPU type the graphics depth the GUI look-and-feel etc. This level is initialized to 700.

Class Level, Level FINE

FINE is a message level providing tracing information.

All of FINE FINER and FINEST are intended for relatively detailed tracing. The exact meaning of the three levels will vary between subsystems but in general FINEST should be used for the most voluminous detailed output FINER for somewhat less detailed output and FINE for the lowest volume (and most important) messages.

In general the FINE level should be used for information that will be broadly interesting to developers who do not have a specialized interest in the specific subsystem.

FINE messages might include things like minor (recoverable) failures. Issues indicating potential performance problems are also worth logging as FINE. This level is initialized to 500.

Class Level, Level FINER

FINER indicates a fairly detailed tracing message. By default logging calls for entering returning or throwing an exception are traced at this level. This level is initialized to 400.
Class Level, Level FINEST

FINEST indicates a highly detailed tracing message. This level is initialized to 300.
Class Level, Level INFO

INFO is a message level for informational messages.

Typically INFO messages will be written to the console or its equivalent. So the INFO level should only be used for reasonably significant messages that will make sense to end users and system admins. This level is initialized to 800.

Class Level, Level OFF

OFF is a special level that can be used to turn off logging. This level is initialized to Integer.MAX_VALUE.
Class Level, Level SEVERE

SEVERE is a message level indicating a serious failure.

In general SEVERE messages should describe events that are of considerable importance and which will prevent normal program execution. They should be reasonably intelligible to end users and to system administrators. This level is initialized to 1000.

Class Level, Level WARNING

WARNING is a message level indicating a potential problem.

In general WARNING messages should describe events that will be of interest to end users or system managers or which indicate potential problems. This level is initialized to 900.


Class LoggingPermission

The permission which the SecurityManager will check when code that is running with a SecurityManager calls one of the logging control methods (such as Logger.setLevel).

Currently there is only one named LoggingPermission. This is "control" and it grants the ability to control the logging configuration for example by adding or removing Handlers by adding or removing Filters or by changing logging levels.

Programmers do not normally create LoggingPermission objects directly. Instead they are created by the security policy code based on reading the security policy file. @version 1.5 126 02/03/01/02 @since 1.4 @see java.security.BasicPermission @see java.security.Permission @see java.security.Permissions @see java.security.PermissionCollection @see java.lang.SecurityManager

Class LoggingPermission, constructor LoggingPermission(String, String)

Creates a new LoggingPermission object. This constructor exists for use by the Policy object to instantiate new Permission objects. @param name Permission name. Must be "control". @param actions Must be either null or the empty string. @throws IllegalArgumentException if arguments are invalid

Class SocketHandler

Simple network logging Handler.

LogRecords are published to a network stream connection. By default the XMLFormatter class is used for formatting.

Configuration: By default each SocketHandler is initialized using the following LogManager configuration properties. If properties are not defined (or have invalid values) then the specified default values are used.

The output IO stream is buffered but is flushed after each LogRecord is written. @version 1.11 12 02/0321/0102 @since 1.4