[ https://issues.jboss.org/browse/WFLY-11166?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11166: ----------------------------------------- [~dmlloyd] I think simply making providing a Service<Void> part of the capability contract of 'org.wildfly.transactions.local-provider' should suffice for ordering issues. Any consumers of the capability that care about ordering can depend on that, but the API for accessing TM etc is the transaction-client API. OT: I think some of the dependencies of the org.wildfly.transaction.client module should be made optional, as they exist to allow outside callers of JBossLocalTransactionProvider.builder() -- i.e. the transactions subsystem -- to do their thing. If there are no such allers, the dependencies are not needed. Those outsider callers can be responsible for ensuring the modules are present. I'll file a JIRA for that unless you disagree. Dunno if that will have any practical benefit, but in theory its nice if the classloading requirement for the API is decoupled from a requirement for the local-provider capability. -- This message was sent by Atlassian Jira (v7.12.1#712002)