logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1547) The Core AbstractConfiguration should track its LoggerContext and add Configuration.getLoggerContext()
Date Thu, 25 Aug 2016 22:45:20 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437862#comment-15437862
] 

Gary Gregory commented on LOG4J2-1547:
--------------------------------------

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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message