Each bundle may have its own named LoggerContext based upon its
bundle symbolic name, bundle version, and bundle location. There is also a
root Logger Context from which each named Logger Context inherits. The root
Logger Context has no name.
When a bundle logs, the logger implementation must locate the Logger Context
for the bundle to determine the
effective log level of the
logger name. The best matching name for the Logger Context is the
longest name, which has a non-empty Logger Context, according to this syntax:
name ::= symbolic-name ( '|' version ( '|' location )? )?The version must be formatted canonically, that is, according to the
toString() method of the Version class. So the Logger Context
for a bundle is searched for using the following names in the given order:
<symbolic-name>|<version>|<location> <symbolic-name>|<version> <symbolic-name>The search stops at the first
non-empty
Logger Context. If no non-empty Logger Context is found using the above
search order, the Logger Context with the symbolic name of the bundle must be
used for the bundle.
| Modifier and Type | Field and Description |
|---|---|
| public static final String | LOG_SERVICE_ID
Logger Admin service property to associate the Logger Admin service with
a |
| Modifier and Type | Method and Description |
|---|---|
| public LoggerContext | Returns: The Logger Context for the specified name. The returned Logger Context may beempty.The name of the Logger Context. Can be name)null to
specify the root Logger Context.Get the Logger Context for the specified name. |
| LOG_SERVICE_ID | back to summary |
|---|---|
| public static final String LOG_SERVICE_ID Logger Admin service property to associate the Logger Admin service with
a
This service property is set to the
The value of this service property must be of type | |
| getLoggerContext | back to summary |
|---|---|
| public LoggerContext getLoggerContext(String name) Get the Logger Context for the specified name.
| |