DefaultCacheManager.defineConfiguration(String, String, Configuration) applies the configurations in the wrong order -------------------------------------------------------------------------------------------------------------------- Key: ISPN-7587 URL: https://issues.jboss.org/browse/ISPN-7587 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.0.0.CR2 Reporter: Dan Berindei Assignee: William Burns Fix For: 9.0.0.Final {{DefaultCacheManager.defineConfiguration(String name, String template, Configuration configurationOverride)}} is supposed to use a template configuration, apply any non-default attributes from {{configurationOverride}}, and define a new cache configuration or template based on the result. However, it reads the override configuration first, so if both the template and the override define the same attribute, the attribute from the template wins.