[jboss-jira] [JBoss JIRA] (WFLY-3227) Replace batching="true|false" with <transaction mode="BATCH"/> in infinispan subsystem schema/model

[Paul Ferraro (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro updated WFLY-3227:
-------------------------------

    Git Pull Request: https://github.com/wildfly/wildfly/pull/6470  (was: https://github.com/wildfly/wildfly/pull/6469)


> Replace batching="true|false" with <transaction mode="BATCH"/> in infinispan subsystem schema/model
> ---------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3227
>                 URL: https://issues.jboss.org/browse/WFLY-3227
>             Project: WildFly
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 8.0.0.Final
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>             Fix For: 9.0.0.CR1
>
>
> Currently, one enables use of Infinispan batching via the batching="true" attribute.  The implications of batching have evolved over time, but currently batching uses the BatchModeTransactionManager, which makes it incompatible with a <transaction mode="..."/> other than NONE.
> To resolve this mutual incompatibility and to remove any ambiguity, I propose replacing the batching attribute with a new transaction mode, i.e. <transaction mode="BATCH"/>.
> The complete list of transaction modes would now be:
> NONE: the cache is not configured with a transaction manager
> BATCH: the cache is configured with a BatchModeTransactionManager
> NON_XA: the cache is configured with WF's transaction manager, but will interact via Synchronizations
> NON_DURABLE_XA: the cache is configured with WF's transaction manager and will interact via an XAResource w/out recovery.
> FULL_XA:  the cache is configured with WF's transaction manager and will interact via an XAResource w/recovery.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)