public class LogKitAdapter extends org.apache.avalon.framework.logger.AbstractLogEnabled implements LoggerManager
| Modifier and Type | Field and Description |
|---|---|
protected org.apache.log.Hierarchy |
m_hierarchy
The hierarchy that really produces loggers.
|
ROLE| Constructor and Description |
|---|
LogKitAdapter(org.apache.log.Hierarchy hierarchy)
Initialized
LogKitAdapter to operate
of a certain LogKit Hierarchy. |
| Modifier and Type | Method and Description |
|---|---|
org.apache.avalon.framework.logger.Logger |
getDefaultLogger()
Return the default Logger.
|
org.apache.avalon.framework.logger.Logger |
getLoggerForCategory(java.lang.String categoryName)
Return the Logger for the specified category.
|
protected final org.apache.log.Hierarchy m_hierarchy
public LogKitAdapter(org.apache.log.Hierarchy hierarchy)
LogKitAdapter to operate
of a certain LogKit Hierarchy.public org.apache.avalon.framework.logger.Logger getLoggerForCategory(java.lang.String categoryName)
In LogKit getRootLogger() and getLoggerFor("") unless the logger for category "" has been explicitly configured return identically configured but different loggers.
Our LogKitConfHelper configures getRootLogger(), not getLoggerFor(""). We think this is a reasonable behavior and expect that LogKit Hierarchies configured by other means then LogKitConfHelper are configured in the same way.
This justifies our decision to return getRootLogger() when given "" category name.
getLoggerForCategory in interface LoggerManagerpublic org.apache.avalon.framework.logger.Logger getDefaultLogger()
getDefaultLogger in interface LoggerManager