[infinispan-issues] [JBoss JIRA] (ISPN-9880) Docs: Hot Rod Transaction Support Feedback

[Don Naro (Jira)]

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

Don Naro updated ISPN-9880:
---------------------------
    Status: Open  (was: New)


> Docs: Hot Rod Transaction Support Feedback
> ------------------------------------------
>
>                 Key: ISPN-9880
>                 URL: https://issues.jboss.org/browse/ISPN-9880
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Documentation-Core
>    Affects Versions: 10.0.0.Beta2, 9.4.6.Final
>            Reporter: Don Naro
>            Assignee: Don Naro
>            Priority: Major
>
> Feedback from Wolf on Hot Rod Transaction docs:
> Server Guide
> - 6.2.6 Transactions 
> Remove: While it is possible to configure server caches to be transactional, none of the available protocols offer transaction capabilities.
> Additionally:
> "to make it simple for the user if you don't highlight to implement a custom TxManager, this is only needed to integrate other implementations.
> If not needed, the GenericTxM is the best choice as it will use our TxM inside EAP or the RemoteTxM if there is nothing found.
> So this will be 99% of the use cases (or more)"
> User Guide
> - 20.7.21.2.2 Transaction Modes
> "The transaction mode names are the same for server configuration and for client settings.
> To prevent from confusion it should be clarified here that this is the client setting
> and the server will not work correctly if the client use Tx but the server has no Tx setting.
> This should fail at runtime if the client request a Tx for a non-tx-cache (but I did not tested this yet)"
> 20.7.21
> "The introducing paragraph and the tip mention that the client side Tx is quasi optimistic.
> But there is no highlighted node that the consistence is possibly affected by that.
> There should be a warning and a link to the detailed description 20.7.21.4 to makes this as clear as possible."



--
This message was sent by Atlassian Jira
(v7.12.1#712002)