Details
-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
None
Description
There is a need in WildFly for a log context selector that short-circuits after the first callers class loader that is not a log API. All log API's would have to be registered. The call stack would be walked and once a class loader is found that is not registered as a log API class loader, that caller would be used to determine whether or not a registered log context should be used. If no context is associated with the caller, the default log context will be used and the call stack walking will stop.
Attachments
Issue Links
- blocks
-
WFCORE-3376 Modules may create loggers on a deployments log context
- Open
- is incorporated by
-
WFCORE-3375 Upgrade jboss-logmanager from 2.1.0.Alpha5 to 2.1.0.Alpha6
- Closed