Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6338

Infinispan subsystem XSD disagrees with TransactionResourceDefinition on default locking mode

    XMLWordPrintable

Details

    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

          clones

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-3722 Infinispan subsystem XSD disagrees with TransactionResourceDefinition on default locking mode

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: WFLY

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved: