logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOG4J2-494) Support composite configurations
Date Sun, 24 Apr 2016 06:43:13 GMT

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

Remko Popma edited comment on LOG4J2-494 at 4/24/16 6:43 AM:
-------------------------------------------------------------

Note that while the Jira spam attack is ongoing you may not be able to comment on this issue.
If that is the case please send your feedback to the log4j-user mailing list with \[LOG4J2-494\]
in the subject.


was (Author: remkop@yahoo.com):
Note that while the Jira spam attack is ongoing you may not be able to comment on this issue.
If that is the case please send your feedback to the log4j-user mailing list with [LOG4J2-494]
in the subject.

> Support composite configurations
> --------------------------------
>
>                 Key: LOG4J2-494
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-494
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Configurators
>    Affects Versions: 2.0-beta9
>            Reporter: Ralph Goers
>            Assignee: Ralph Goers
>
> Support was added to XMLConfiguration to allow XIncludes in the XML files. While this
can be useful it does not allow for the use case where someone wants a default configuration
and then a custom configuration to be merged with it.
> I am proposing creating a CompositeConfiguration class that accepts a comma separated
list of configuration files. It would then use the Configuration factories to create the appropriate
Configuration classes for each of the underlying files.  It would then merge the Node hierarchies
created by each into a single tree and then finally construct the actual configuration Objects
from that tree.
> There are a few issues with this - for example each configuration can specify debug and
verbose attributes, duplicate property settings, handling duplicate Appender names, etc. 
Most of these should be fairly easy to resolve.



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