[
https://issues.apache.org/jira/browse/LOG4J2-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438417#comment-15438417
]
Gary Gregory commented on LOG4J2-1547:
--------------------------------------
Hi Remko:
When I think of programmatic configuration I think of the new API we introduced
with https://logging.apache.org/log4j/2.x/manual/customconfig.html
You must mean the addition of the LoggerContext parameter to the APIs:
-
org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(LoggerContext,
ConfigurationSource)
-
org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(LoggerContext,
String, URI)
-
org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(LoggerContext,
String, URI, ClassLoader)
You mean document this change? And where does the LoggerContext argument should
come from? Yeah... where should it come from...?
I want to make sure I understand exactly what you mean :-)
Gary
> 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]
