When accessing configuration templates, there might be use cases, where programmatic code wants to explicitly override some of the config that is provided by default. Similarly there might be use cases, where parts of the configuration is not managed by the Tamaya ConfigurationManager. When injecting configuration into beans, accessing templates as well as resolving expressions, it must be possible to provide overriding configurations as well.
Similarly this would also simplify testing a lot.
This would be easily done by the following changes in Configuration (and subsequent elements in the chain):