[
https://issues.jboss.org/browse/WFLY-11166?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-11166:
-----------------------------------------
[~dmlloyd] Is this more of a capability naming issue then? For example, not static
capability "org.wildfly.transactions.transaction-manager" but rather a dynamic
one "org.wildfly.transactions.local-provider.transaction-manager" and then the
dynamic part for now is always "narayana"?
That's a mouthful of a capability name, but oh well. :)
Re: "if no subsystem provides the capability, the system may still be usable",
that's an issue for the consumer of the capability. If it's not required they can
check for the capability presence and proceed without.
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)