[
https://issues.apache.org/jira/browse/LOG4J2-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112613#comment-14112613
]
Alex Barnes commented on LOG4J2-804:
------------------------------------
I'm happy with any strategy so long as it provides enough flexibility for
sharing/merging config. The current XInclude strategy is severely limited in
its capabilities and appears to currently be the only way.
> XInclude does not respect classpath
> -----------------------------------
>
> Key: LOG4J2-804
> URL: https://issues.apache.org/jira/browse/LOG4J2-804
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Reporter: Alex Barnes
>
> This issue is related to the one resolved by
> https://issues.apache.org/jira/browse/LOG4J2-341
> The <xi:include> element does not respect entries provided on the classpath.
> Specific use case: I have a log4j2.xml configuration I wish to share across
> several applications providing a common base of appenders and plugins, these
> are bundled into a myorg-logging.jar to be used in downstream projects that
> wish to provide configuration for their loggers. In the myorg-logging
> log4j2.xml I wish to optionally include a file from the classpath called
> myorg-logging.xml
> == log4j2.xml ==
> <Loggers>
> <logger name="root" level="env:rootLogLevel:-WARN"/>
> <logger name="my.org" level="env:myOrgLogLevel:-INFO"/>
> <xi:include href="myorg-logging.xml">
> <xi:fallback/>
> </xi:include>
> </Loggers>
> I also noticed once a Loggers or Appenders section has been declared in xml,
> it can not be appended to with a second Loggers or Appenders section (which
> would be nice for a top level additive xi:include scenario instead of
> limiting to an included file just for loggers, a file just for appenders, etc)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
