forked from hazelcast/hazelcast
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix regression in declarative config file resolution
3.12 introduced a regression that configuration files with suffixes not in [xml,yaml,yml] passed in system property are ignored silently and the config resolution continues following the resolution priority, most likely resolving the default XML configuration shipped with the jar. The expected behavior is: - if the system property is set we fail fast if we can't load the config from the referenced resource/file - if the file in the system property has a suffix [yaml,yml], we treat it as YAML config - if the file in the system property has any other suffix (or don't have suffix), we treat it as XML config Note that in 4.0 the fix will be different, we enforce the config files to have suffix from the [xml,yaml,yml] list. This commit fixes this behavior in member, client and client-failover config resolution, with additional tests verifying the resolution logic. Fixes hazelcast#14924
- Loading branch information
Showing
39 changed files
with
2,357 additions
and
37 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.