[
https://issues.jboss.org/browse/WFLY-11166?page=com.atlassian.jira.plugin...
]
David Lloyd commented on WFLY-11166:
------------------------------------
Even this one subtask might be a bit more complex than it appears. The three types
mentioned in the summary are _always_ available, thanks to the transaction client library.
The real capability from the perspective of the usage of these three types is the local
transaction provider, which would normally come from the org.jboss.as.transaction
extension.
And yet, if no subsystem provides the capability, the system may still be usable. The
transaction client library will still function, though certain transaction-related
operations will obviously be disallowed. Additionally, it's not impossible that at
some point in the future we may support more than one local transaction provider at once,
with an application- or component-specific manner of selecting the provider to use.
Create capabilities for TransactionManager, UserTransaction and
TransactionSynchronizationRegistry
--------------------------------------------------------------------------------------------------
Key: WFLY-11166
URL:
https://issues.jboss.org/browse/WFLY-11166
Project: WildFly
Issue Type: Sub-task
Components: Management, Transactions
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Major
See
https://issues.jboss.org/browse/WFLY-9587?focusedCommentId=13647549&p...
in the parent issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)