Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-3722

Infinispan subsystem XSD disagrees with TransactionResourceDefinition on default locking mode

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.0.0.ER7
    • 7.0.0.ER6
    • Clustering
    • None

    Description

      The XSD for the Infinispan subsystem (jboss-as-infinispan_4_0.xsd) says that the default locking level is OPTIMISTIC:

      <xs:complexType name="transaction">
          ...
          <xs:attribute name="locking" type="tns:locking-mode" default="OPTIMISTIC">
              <xs:annotation>
                  <xs:documentation>The locking mode for this cache, one of OPTIMISTIC or PESSIMISTIC.</xs:documentation>
              </xs:annotation>
          </xs:attribute>
      </xs:complexType>
      

      However, the TransactionResourceDefinition class, which is the ultimate source of truth, disagrees:

      enum Attribute implements org.jboss.as.clustering.controller.Attribute {
          LOCKING("locking", ModelType.STRING, new ModelNode(LockingMode.PESSIMISTIC.name()), new EnumValidatorBuilder<>(LockingMode.class)),
          ...
      }
      

      I'm not sure myself which one should be the default, but this difference is surely a bug.

      Attachments

        Issue Links

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              mvinkler1@redhat.com Michal Vinkler
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: