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

Parser sets transaction().useSynchronization to non-default value

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 9.0.0.Final
    • 8.0.1.Final
    • Configuration
    • None

      Default value for transaction().useSynchronization() is false, so when the configuration is build programmatically, it is set to false. However, if I configure a non-transactional cache in XML and read the configuration, it is set to true.

      This complicates testing, when I want to compare programmatic and XML configurations, and generally it is inconsistent.

      When doing equals() operation on configurations. transaction-only attributes should not be compared if transactionMode == NONE, since they actually don't matter.

              Unassigned Unassigned
              rvansa1@redhat.com Radim Vansa (Inactive)
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: