[ https://issues.jboss.org/browse/WFLY-9587?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-9587: ---------------------------------------- As part of our work on getting maximum benefit from Galleon, we want to eliminate unnecessary hard dependencies between modules, and a good candidate for that is dependencies on the org.jboss.as.transactions module. See WFLY-11165. This JIRA has some complex aspects, e.g. JTS or perhaps capabilities for some less commonly used services provided by the subsystem. But there are a couple simpler cases that if handled will go a very long way toward eliminating most uses of org.jboss.as.transactions. So I'd like to create subtasks for these and get them sorted today: 1) TransactionManager and TransactionSynchronizationRegistry. The services for these are always installed if the subsystem is installed and the service value type are clearly "stable" API classes. So it seems trivial to add a capability for these. 2) XAResourceRecoveryRegistry. The service for this is always installed if the subsystem is installed. The service value type is not as obviously "stable" as TransactionManager and TransactionSynchronizationRegistry, so I think this should be a separate issue to allow it to be rejected etc if not wanted. -- This message was sent by Atlassian Jira (v7.12.1#712002)