[
https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437862#comment-15437862
]
Gary Gregory edited comment on LOG4J2-1547 at 8/25/16 10:45 PM:
----------------------------------------------------------------
The problem is there is apparently not a reliable way to make sure you end up
the right logger context. This is why you cannot just add a getLoggerContext()
method in AbstractManager that says {{return LoggerContext.getContext(false);}}
see
https://issues.apache.org/jira/browse/LOG4J2-1539?focusedCommentId=15431822&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15431822
was (Author: garydgregory):
The problem is there is apparently not a reliable way to make sure you end up
the right logger context. This is why you cannot just add a getLoggerContext()
method in AbstractManager that says {{return LoggerContext.getContext(false);}}
> The Core AbstractConfiguration should track its LoggerContext and add
> Configuration.getLoggerContext()
> ------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1547
> URL: https://issues.apache.org/jira/browse/LOG4J2-1547
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Attachments: logging-log4j2.patch
>
>
> The class in Core, {{AbstractConfiguration}}, should track its
> {{LoggerContext}} and provide it with a new API
> {{Configuration.getLoggerContext()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
