Guys,

Have you looked at Apache Commons Config 2 lately?
https://commons.apache.org/proper/commons-configuration/apidocs/org/apache/commons/configuration2/builder/combined/CombinedConfigurationBuilder.html
(actually that's been around since 1.3) shows a lot of similarities with
the ideas for "configuration metadata" or chaining and ordering
configuration sources.

It still seems a little less targeting true distributed configuration and
configuration sources. Configuration there is always mutable btw. (unless
you stick to the ImmutableConfiguration base interface, that's very similar
to what JCache did with its config subsystem)

Cheers,

Werner


On Tue, Jan 3, 2017 at 5:37 PM, Werner Keil <[email protected]> wrote:

> cfg4j uses a slightly different approach called "fallback" so you create a
> FallbackConfigurationSource (sounds familiar, probably where the name was
> derived from, at least neither DeltaSpike nor Tamaya know a term
> ConfigSource or ConfigurationSource;-) with n fallbacks. The order is
> likely defined there simly by how you create such array of fallback config
> sources.
>

Reply via email to