declare namespace java { namespace util { namespace logging { /** * There is a single global LogManager object that is used to * maintain a set of shared state about Loggers and log services. *

* This LogManager object: *

*

* The global LogManager object can be retrieved using LogManager.getLogManager(). * The LogManager object is created during class initialization and * cannot subsequently be changed. *

* At startup the LogManager class is located using the * java.util.logging.manager system property. *

* The LogManager defines two optional system properties that allow control over * the initial configuration: *

* These two properties may be specified on the command line to the "java" * command, or as system property definitions passed to JNI_CreateJavaVM. *

* If the "java.util.logging.config.class" property is set, then the * property value is treated as a class name. The given class will be * loaded, an object will be instantiated, and that object's constructor * is responsible for reading in the initial configuration. (That object * may use other system properties to control its configuration.) The * alternate configuration class can use readConfiguration(InputStream) * to define properties in the LogManager. *

* If "java.util.logging.config.class" property is not set, * then the "java.util.logging.config.file" system property can be used * to specify a properties file (in java.util.Properties format). The * initial logging configuration will be read from this file. *

* If neither of these properties is defined then the LogManager uses its * default configuration. The default configuration is typically loaded from the * properties file "{@code lib/logging.properties}" in the Java installation * directory. *

* The properties for loggers and Handlers will have names starting * with the dot-separated name for the handler or logger. *

* The global logging properties may include: *

*

* Note that all classes loaded during LogManager configuration are * first searched on the system class path before any user class path. * That includes the LogManager class, any config classes, and any * handler classes. *

* Loggers are organized into a naming hierarchy based on their * dot separated names. Thus "a.b.c" is a child of "a.b", but * "a.b1" and a.b2" are peers. *

* All properties whose names end with ".level" are assumed to define * log levels for Loggers. Thus "foo.level" defines a log level for * the logger called "foo" and (recursively) for any of its children * in the naming hierarchy. Log Levels are applied in the order they * are defined in the properties file. Thus level settings for child * nodes in the tree should come after settings for their parents. * The property name ".level" can be used to set the level for the * root of the tree. *

* All methods on the LogManager object are multi-thread safe. * @since 1.4 */ // @ts-ignore class LogManager extends java.lang.Object { /** * Protected constructor. This is protected so that container applications * (such as J2EE containers) can subclass the object. It is non-public as * it is intended that there only be one LogManager object, whose value is * retrieved by calling LogManager.getLogManager. */ // @ts-ignore constructor() /** * String representation of the * {@link javax.management.ObjectName} for the management interface * for the logging facility. * @see java.lang.management.PlatformLoggingMXBean * @see java.util.logging.LoggingMXBean * @since 1.5 */ // @ts-ignore public static readonly LOGGING_MXBEAN_NAME: java.lang.String | string /** * Returns the global LogManager object. * @return the global LogManager object */ // @ts-ignore public static getLogManager(): java.util.logging.LogManager /** * Adds an event listener to be invoked when the logging * properties are re-read. Adding multiple instances of * the same event Listener results in multiple entries * in the property event listener table. *

WARNING: This method is omitted from this class in all subset * Profiles of Java SE that do not include the {@code java.beans} package. *

* @param l event listener * @exception SecurityException if a security manager exists and if * the caller does not have LoggingPermission("control"). * @exception NullPointerException if the PropertyChangeListener is null. * @deprecated The dependency on {#code PropertyChangeListener} creates a * significant impediment to future modularization of the Java * platform. This method will be removed in a future release. * The global {@code LogManager} can detect changes to the * logging configuration by overridding the {@link * #readConfiguration readConfiguration} method. */ // @ts-ignore public addPropertyChangeListener(l: java.beans.PropertyChangeListener): void /** * Removes an event listener for property change events. * If the same listener instance has been added to the listener table * through multiple invocations of addPropertyChangeListener, * then an equivalent number of * removePropertyChangeListener invocations are required to remove * all instances of that listener from the listener table. *

* Returns silently if the given listener is not found. *

WARNING: This method is omitted from this class in all subset * Profiles of Java SE that do not include the {@code java.beans} package. *

* @param l event listener (can be null) * @exception SecurityException if a security manager exists and if * the caller does not have LoggingPermission("control"). * @deprecated The dependency on {#code PropertyChangeListener} creates a * significant impediment to future modularization of the Java * platform. This method will be removed in a future release. * The global {@code LogManager} can detect changes to the * logging configuration by overridding the {@link * #readConfiguration readConfiguration} method. */ // @ts-ignore public removePropertyChangeListener(l: java.beans.PropertyChangeListener): void /** * Add a named logger. This does nothing and returns false if a logger * with the same name is already registered. *

* The Logger factory methods call this method to register each * newly created Logger. *

* The application should retain its own reference to the Logger * object to avoid it being garbage collected. The LogManager * may only retain a weak reference. * @param logger the new logger. * @return true if the argument logger was registered successfully, * false if a logger of that name already exists. * @exception NullPointerException if the logger name is null. */ // @ts-ignore public addLogger(logger: java.util.logging.Logger): boolean /** * Method to find a named logger. *

* Note that since untrusted code may create loggers with * arbitrary names this method should not be relied on to * find Loggers for security sensitive logging. * It is also important to note that the Logger associated with the * String {@code name} may be garbage collected at any time if there * is no strong reference to the Logger. The caller of this method * must check the return value for null in order to properly handle * the case where the Logger has been garbage collected. *

* @param name name of the logger * @return matching logger or null if none is found */ // @ts-ignore public getLogger(name: java.lang.String | string): java.util.logging.Logger /** * Get an enumeration of known logger names. *

* Note: Loggers may be added dynamically as new classes are loaded. * This method only reports on the loggers that are currently registered. * It is also important to note that this method only returns the name * of a Logger, not a strong reference to the Logger itself. * The returned String does nothing to prevent the Logger from being * garbage collected. In particular, if the returned name is passed * to {@code LogManager.getLogger()}, then the caller must check the * return value from {@code LogManager.getLogger()} for null to properly * handle the case where the Logger has been garbage collected in the * time since its name was returned by this method. *

* @return enumeration of logger name strings */ // @ts-ignore public getLoggerNames(): java.util.Enumeration /** * Reinitialize the logging properties and reread the logging configuration. *

* The same rules are used for locating the configuration properties * as are used at startup. So normally the logging properties will * be re-read from the same file that was used at startup. *

* Any log level definitions in the new configuration file will be * applied using Logger.setLevel(), if the target Logger exists. *

* A PropertyChangeEvent will be fired after the properties are read. * @exception SecurityException if a security manager exists and if * the caller does not have LoggingPermission("control"). * @exception IOException if there are IO problems reading the configuration. */ // @ts-ignore public readConfiguration(): void /** * Reset the logging configuration. *

* For all named loggers, the reset operation removes and closes * all Handlers and (except for the root logger) sets the level * to null. The root logger's level is set to Level.INFO. * @exception SecurityException if a security manager exists and if * the caller does not have LoggingPermission("control"). */ // @ts-ignore public reset(): void /** * Reinitialize the logging properties and reread the logging configuration * from the given stream, which should be in java.util.Properties format. * A PropertyChangeEvent will be fired after the properties are read. *

* Any log level definitions in the new configuration file will be * applied using Logger.setLevel(), if the target Logger exists. * @param ins stream to read properties from * @exception SecurityException if a security manager exists and if * the caller does not have LoggingPermission("control"). * @exception IOException if there are problems reading from the stream. */ // @ts-ignore public readConfiguration(ins: java.io.InputStream): void /** * Get the value of a logging property. * The method returns null if the property is not found. * @param name property name * @return property value */ // @ts-ignore public getProperty(name: java.lang.String | string): string /** * Check that the current context is trusted to modify the logging * configuration. This requires LoggingPermission("control"). *

* If the check fails we throw a SecurityException, otherwise * we return normally. * @exception SecurityException if a security manager exists and if * the caller does not have LoggingPermission("control"). */ // @ts-ignore public checkAccess(): void /** * Returns LoggingMXBean for managing loggers. * An alternative way to manage loggers is through the * {@link java.lang.management.PlatformLoggingMXBean} interface * that can be obtained by calling: *

                 * PlatformLoggingMXBean logging = {@link java.lang.management.ManagementFactory#getPlatformMXBean(Class)
                 * ManagementFactory.getPlatformMXBean}(PlatformLoggingMXBean.class);
                 * 
* @return a {#link LoggingMXBean} object. * @see java.lang.management.PlatformLoggingMXBean * @since 1.5 */ // @ts-ignore public static getLoggingMXBean(): java.util.logging.LoggingMXBean } } } }