ArchaiusConfigurationProvider owns all properties even they are not defined.

[metacret]

When I use CompositeConfigurationProvider such as the following code:

binder.bindConfigurationProvider().toInstance(
                                                new CompositeConfigurationProvider(
                                                        ArchaiusConfigurationProvider.builder().build(),
                                                        new PropertiesConfigurationProvider(properties)));

ArchaiusConfigurationProvider owns all properties even they are not defined. If the property is not defined in Archaius, it should fall back to other configuration provider chained above.

The temporary solution can be the following:

ConfigurationOwnershipPolicy ownershipPolicy = new ConfigurationOwnershipPolicy() {
                                            @Override
                                            public boolean has(ConfigurationKey key, Map<String, String> variableValues) {
                                                return !properties.containsKey(key.getKey(variableValues));
                                            }
                                        };

and hook up the above ownershipPolicy with ArchiausConfigurationProvider at withOwnershipPolicy.

[metacret]

With null specifically withOwnershipPolicy(null), it shows the behavior of the previous version(v1.1.1). I think we'd better document this. If null parameter is not ugly, you can close this issue.

[elandau]

Initially I was thinking of changing the default ownership policy to 'null' so that archaius only claims ownership of properties that have been specified at startup. I think now that this will just further confuse things. I think a better approach would be to document that archaius (or any dynamic property source) shouldn't be used with CompoisteConfigurationProvider. The reason for this is that CompositeConfigurationProvider is meant to be used for disjoint sets of properties and mixing it with ArhcaiusConfigurationProvider just confuses things because archaius itself manages properties from multiple sources. With CompositeConfigurationProvider It is difficult to determine which provider owns a property that was not specified at startup but should be picked up dynamically.

Alternatively you could specify a regex for ArchaiusConfigurationProvider to only own properties with a certain prefix.

[Randgalt]

That's fine with me. Eran, please update the wiki/doc

[Randgalt]

@elandau any news on this or should we close the issue?