@ProviderType public interface LoggerAdmin
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
Versionclass. 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-emptyLogger 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|
Logger Admin service property to associate the Logger Admin service with a
static final java.lang.String LOG_SERVICE_ID
This service property is set to the
service.id for the
LoggerFactory service administered by this Logger Admin.
The value of this service property must be of type
LoggerContext getLoggerContext(java.lang.String name)
name- The name of the Logger Context. Can be
nullto specify the root Logger Context.
Copyright © OSGi Alliance (2000, 2018). All Rights Reserved. Licensed under the OSGi Specification License, Version 2.0