When a LogRecord is passed into the logging framework it logically belongs to the framework and should no longer be used or updated by the client application.
Note that if the client application has not specified an explicit source method name and source class name, then the LogRecord class will infer them automatically when they are first accessed (due to a call on getSourceMethodName or getSourceClassName) by analyzing the call stack. Therefore, if a logging Handler wants to pass off a LogRecord to another thread, or to transmit it over RMI, and if it wishes to subsequently obtain method name or class name information it should call one of getSourceClassName or getSourceMethodName to force the values to be filled in.
LogRecord are never null; if some attributes are not set (e.g. logger name, or rendered cause taken from Throwable) empty strings are returned.
The is a holder object that may be setup using the setValue() and re-used rather than creating a new object for each actual log record.
The format of a log record is @derby.formatId LOG_RECORDthe formatId is written by FormatIdOutputStream when this object is written out by writeObject @derby.purpose The log record described every change to the persistent store @derby.upgrade @derby.diskLayout loggable group(CompressedInt) the loggable's group value xactId(TransactionId) The Transaction this log belongs to op(Loggable) the log operation @derby.endFormat
This class may be extended by applications to provide Java Bean mappings for application data fields within the record. @author Michael Giroux