-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b128
-
Verified
Because Loggers created by system classes and loggers created by applications are held in two separate namespaces, it makes it hard for an application to configure a system logger.
- If the system class creates the logger first, then the application will get the system logger and everything will be fine.
- If the application creates the logger first, then the system class will get a different logger, and the configuration of the application logger will be initially copied over to the system logger.
However, not all configuration is copied: only the handlers. Level and useParentHandler and filters are not copied.
- If the system class creates the logger first, then the application will get the system logger and everything will be fine.
- If the application creates the logger first, then the system class will get a different logger, and the configuration of the application logger will be initially copied over to the system logger.
However, not all configuration is copied: only the handlers. Level and useParentHandler and filters are not copied.
- duplicates
-
JDK-8023163 Logger hierarchy inconsistent with applets
-
- Closed
-
-
JDK-8023163 Logger hierarchy inconsistent with applets
-
- Closed
-
- relates to
-
JDK-8023163 Logger hierarchy inconsistent with applets
-
- Closed
-