org.apache.log4j
public class LogManager extends Object
LogManager
class to retreive Logger
instances or to operate on the current LoggerRepository. When the LogManager
class is loaded
into memory the default initalzation procedure is inititated. The
default intialization procedure is described in the short log4j manual.
Field Summary | |
---|---|
static String | CONFIGURATOR_CLASS_KEY |
static String | DEFAULT_CONFIGURATION_FILE |
static String | DEFAULT_CONFIGURATION_KEY |
static String | DEFAULT_INIT_OVERRIDE_KEY |
Method Summary | |
---|---|
static Logger | exists(String name) |
static Enumeration | getCurrentLoggers() |
static Logger | getLogger(String name)
Retrieve the appropriate Logger instance. |
static Logger | getLogger(Class clazz)
Retrieve the appropriate Logger instance. |
static Logger | getLogger(String name, LoggerFactory factory)
Retrieve the appropriate Logger instance. |
static LoggerRepository | getLoggerRepository() |
static Logger | getRootLogger()
Retrieve the appropriate root logger. |
static void | resetConfiguration() |
static void | setRepositorySelector(RepositorySelector selector, Object guard)
Sets LoggerFactory but only if the correct
guard is passed as parameter.
|
static void | shutdown() |
Deprecated: This variable is for internal use only. It will become private in future versions.
Deprecated: This variable is for internal use only. It will become package protected in future versions.
Deprecated: This variable is for internal use only. It will become private in future versions.
Deprecated: This variable is for internal use only. It will become private in future versions.
LoggerFactory
but only if the correct
guard is passed as parameter.
Initally the guard is null. If the guard is
null
, then invoking this method sets the logger
factory and the guard. Following invocations will throw a IllegalArgumentException, unless the previously set
guard
is passed as the second parameter.
This allows a high-level component to set the RepositorySelector used by the LogManager
.
For example, when tomcat starts it will be able to install its own repository selector. However, if and when Tomcat is embedded within JBoss, then JBoss will install its own repository selector and Tomcat will use the repository selector set by its container, JBoss.