[
https://issues.jboss.org/browse/ISPN-10683?page=com.atlassian.jira.plugin...
]
Pedro Ruivo commented on ISPN-10683:
------------------------------------
{{GlobalTransaction}} doesn't give the user any information about the transaction that
failed because:
* there's no mapping between gtx and tx
* gtx is created internally.
In addition, the only method that may make sense to invoke in the {{Transaction}} class is
the register/unregister the sync/xa resources. All other methods are useless in this
context.
Remove CustomFailurePolicy transaction parameters
-------------------------------------------------
Key: ISPN-10683
URL:
https://issues.jboss.org/browse/ISPN-10683
Project: Infinispan
Issue Type: Task
Components: Core
Affects Versions: 10.0.0.CR2
Reporter: Dan Berindei
Priority: Major
Fix For: 10.0.0.Final
The {{CustomFailurePolicy}} javadoc says it should be thread-safe, but the
{{javax.transaction.Transaction}} javadoc doesn't say anything about thread safety.
We should replace the {{javax.transaction.Transaction}} with a {{GlobalTransaction}},
which we know is thread-safe.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)