You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gisle Grimen (Jira)" <ji...@apache.org> on 2020/03/04 09:44:00 UTC

[jira] [Created] (CONFIGURATION-782) OverrideCombiner does not work properly when key contains list

Gisle Grimen created CONFIGURATION-782:
------------------------------------------

             Summary: OverrideCombiner does not work properly when key contains list
                 Key: CONFIGURATION-782
                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-782
             Project: Commons Configuration
          Issue Type: Bug
          Components: Format
            Reporter: Gisle Grimen


It seems that the OverrideCombiner does not work properly in some cases when key contains a list. The problem is best illustrated with an example:

 

In your Base Config File you following key values:

idp.auth.methods = NO-BANKID, NO-BANKID-MOBILE

And in our Specialty configuration, the one that overrides duplicates in the base config file contains following key:

idp.auth.methods.1443 = SE-BANKID, SE-BANKID-MOBILE

 

The expected result after combining these two configuration files would be:

 

idp.auth.methods = NO-BANKID, NO-BANKID-MOBILE

idp.auth.methods.1443 = SE-BANKID, SE-BANKID-MOBILE

 

However the actual result of current implementation is as follows:

idp.auth.methods.1443 = SE-BANKID, SE-BANKID-MOBILE

 

So even though that the config file that overrides the base configuration file does not have any overriding configuration for idp.auth.methods. The config in the base config connected to key idp.autyh.methods are not added to the combined configuration.

 

If this is not a bug but a feature, then i would like to know which combiner i should use as it is not obvious from the documentation. The objective is to be able to have one file that contains extra configuration which also can include configuration keys that should override configuration keys from the base configuration file.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)