[jboss-jira] [JBoss JIRA] (WFLY-9587) Investigate and introduce capabilities for the transactional subsytems transations/xts/rts

[Brian Stansberry (Jira)]

    [ https://issues.jboss.org/browse/WFLY-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647549#comment-13647549 ] 

Brian Stansberry edited comment on WFLY-9587 at 10/12/18 1:41 PM:
------------------------------------------------------------------

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, UserTransaction 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.


was (Author: brian.stansberry):
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.

> Investigate and introduce capabilities for the transactional subsytems transations/xts/rts
> ------------------------------------------------------------------------------------------
>
>                 Key: WFLY-9587
>                 URL: https://issues.jboss.org/browse/WFLY-9587
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Transactions, XTS
>    Affects Versions: 11.0.0.Final
>            Reporter: Ondra Chaloupka
>            Assignee: Ondra Chaloupka
>            Priority: Major
>
> The notion of capability is not introduced to the transactional system. The WFLY integration expecting subsystem providing it. The transaction subsystems should support so.
> https://docs.jboss.org/author/display/WFLY/Working+with+WildFly+Capabilities



--
This message was sent by Atlassian Jira
(v7.12.1#712002)