You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by "Matt Sicker (JIRA)" <ji...@apache.org> on 2016/03/08 21:20:40 UTC

[jira] [Commented] (LOG4J2-586) Capability to merge LoggerContexts or dynamically add an additional ConfigurationSource to a context.

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

Matt Sicker commented on LOG4J2-586:
------------------------------------

This sounds like a duplicate of LOG4J2-494 or would otherwise be addressed by it.

> Capability to merge LoggerContexts or dynamically add an additional ConfigurationSource to a context.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-586
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-586
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Configurators
>    Affects Versions: 2.0-rc1, 2.1
>            Reporter: James Hutton
>              Labels: features
>
> Looking to use log4j2 in a spring application that uses profiles, which historically used the DOMConfigurator to pull in profile specific log4j.xml's.  Ask is for a similar feature (not xinclude) that could be issued at runtime.  Not looking to reconfigure any loggers, just create a logger context from the additional file and then merge it into the root (or any) logger context.



--
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