The logging methods are grouped in five main categories:
- There are a set of "log" methods that take a log level, a message string, and optionally some parameters to the message string.
- here are a set of "logp" methods (for "log precise") that are like the "log" methods, but also take an explicit source class name and method name.
- There are a set of "logrb" method (for "log with resource bundle") that are like the "logp" method, but also take an explicit resource bundle name for use in localizing the log message.
- There are convenience methods for tracing method entries (the "entering" methods), method returns (the "exiting" methods) and throwing exceptions (the "throwing" methods).
- Finally, there are a set of convenience methods for use in the very simplest cases, when a developer simply wants to log a simple string at a given log level. These methods are named after the standard Level names ("severe", "warning", "info", etc.) and take a single argument, a message string.
For the methods that do not take an explicit source name and method name, the Logging framework will make a "best effort" to determine which class and method called into the logging method. However, it is important to realize that this automatically inferred information may only be approximate (or even wrong). Virtual machines are allowed to do extensive optimizations when JITing and may entirely remove stack frames, making it impossible to reliably locate the calling class and method.
All methods on Logger are multi-thread safe.
The Lotus® Expeditor logging framework leverages the JSR47 implementation provided with the runtime JRE (JRE 1.5). It works directly with java.util.logging.LogRecord
Using NL characters with JSR 47 logging on devices may cause unexpected results. ISO-8859-1 characters are recommended.
For more detailed information on JRE Logging APIs, please see the Sun Javadoc at http://java.sun.com/j2se/1.4.2/docs/
Parent topic: Developing serviceability logic: XPD622