[jboss-jira] [JBoss JIRA] (WFLY-6338) Infinispan subsystem XSD disagrees with TransactionResourceDefinition on default locking mode

[Radoslav Husar (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174056#comment-13174056 ] 

Radoslav Husar commented on WFLY-6338:
--------------------------------------

BTW one way to check for the value actually used without going through code is via CLI

{code}
[standalone at localhost:9990 /] /subsystem=infinispan/cache-container=web/distributed-cache=dist/component=transaction:read-attribute(name=locking,include-defaults=false
{
    "outcome" => "success",
    "result" => undefined
}
[standalone at localhost:9990 /] /subsystem=infinispan/cache-container=web/distributed-cache=dist/component=transaction:read-attribute(name=locking,include-defaults=true
{
    "outcome" => "success",
    "result" => "PESSIMISTIC"
}
{code}


> Infinispan subsystem XSD disagrees with TransactionResourceDefinition on default locking mode
> ---------------------------------------------------------------------------------------------
>
>                 Key: WFLY-6338
>                 URL: https://issues.jboss.org/browse/WFLY-6338
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 10.0.0.Final
>            Reporter: Michal Vinkler
>            Assignee: Radoslav Husar
>            Priority: Blocker
>
> The XSD for the Infinispan subsystem ([jboss-as-infinispan_4_0.xsd|https://github.com/jbossas/jboss-eap7/blob/7.x/clustering/infinispan/extension/src/main/resources/schema/jboss-as-infinispan_4_0.xsd]) says that the default locking level is {{OPTIMISTIC}}:
> {code:xml}
> <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>
> {code}
> However, the [TransactionResourceDefinition|https://github.com/jbossas/jboss-eap7/blob/7.x/clustering/infinispan/extension/src/main/java/org/jboss/as/clustering/infinispan/subsystem/TransactionResourceDefinition.java] class, which is the ultimate source of truth, disagrees:
> {code:java}
> enum Attribute implements org.jboss.as.clustering.controller.Attribute {
>     LOCKING("locking", ModelType.STRING, new ModelNode(LockingMode.PESSIMISTIC.name()), new EnumValidatorBuilder<>(LockingMode.class)),
>     ...
> }
> {code}
> I'm not sure myself which one should be the default, but this difference is surely a bug.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)