Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-7587

DefaultCacheManager.defineConfiguration(String, String, Configuration) applies the configurations in the wrong order

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 9.0.0.CR4
    • 9.0.0.CR2
    • Core
    • None

    Description

      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.

      Attachments

        Activity

          People

            wburns@redhat.com Will Burns
            dberinde@redhat.com Dan Berindei (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: