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

Alex Barnes edited comment on LOG4J2-804 at 8/28/14 1:35 AM:
-------------------------------------------------------------

Maybe the correct course of action is to not rely on xerces to do the heavy 
lifting here and instead of relying solely on xinclude, support a custom 
include mechanism. Logback felt it was important enough... 
http://logback.qos.ch/manual/configuration.html#fileInclusion


was (Author: wizardofzot):
Maybe the correct course of action is to not rely on xerces to do the heavy 
lifting here and instead of relying solely on xinclude, support a custom 
include mechanism. The guys managing Logback felt it was important enough... 
http://logback.qos.ch/manual/configuration.html#fileInclusion

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

Reply via email to