Anton Korenkov created LOG4J2-2674:
--------------------------------------
Summary: CompositeConfiguration misleading configuration source
Key: LOG4J2-2674
URL: https://issues.apache.org/jira/browse/LOG4J2-2674
Project: Log4j 2
Issue Type: Question
Components: Core
Affects Versions: 2.8.1
Reporter: Anton Korenkov
Sometimes we are using CompositeConfiguration in our code. During last
investigation we've found out that configuration source passed during
constructor call is 'NULL_SOURCE'. It's a bit confusing because it conflicts
with NULL_SOURCE definition
{noformat}
/**
* ConfigurationSource to use with Configurations that do not require a
"real" configuration source.
*/
public static final ConfigurationSource NULL_SOURCE = new
ConfigurationSource(new byte[0]);
{noformat}
because actually we have a 'composite' or 'multiple' configuration sources
which will be used later to produce real configuration.
The question is: do you mind to create 'COMPOSITE_SOURCE' constant and use it
in CompositeConfiguration?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
