[jbossts-issues] [JBoss JIRA] (JBTM-2853) Transaction bridging for WS not working because of switch to new wfly transaction client

Anonymous (JIRA) issues at jboss.org
Thu Feb 23 04:16:00 EST 2017


     [ https://issues.jboss.org/browse/JBTM-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Issue was automatically transitioned when chalda created pull request #19 in GitHub
-----------------------------------------------------------------------------------
    Status: Pull Request Sent  (was: Open)


> Transaction bridging for WS not working because of switch to new wfly transaction client
> ----------------------------------------------------------------------------------------
>
>                 Key: JBTM-2853
>                 URL: https://issues.jboss.org/browse/JBTM-2853
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: TxBridge
>    Affects Versions: 5.5.2.Final
>            Reporter: Ondra Chaloupka
>            Assignee: Ondra Chaloupka
>            Priority: Blocker
>
> Transaction bridging (WS transaction <-> global container transaction) does not work currently as container is impacted by switch from transaction spi (https://github.com/jbosstm/jboss-transaction-spi) to wildfly transaction client (https://github.com/wildfly/wildfly-transaction-client).
> The cause code change could be checked here
> https://github.com/wildfly/wildfly/commit/5eb816e0b58da3e99bfee81715ba27b65e8c75fc
> Narayana needs to be enhanced to use the new transaction client to import transaction and bridge the ws to container transaction that way. The similar thing will probably need to be done for opposite side.
> Container integration code in jboss container needs to be changed in way to provide the transaction context to Narayana.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbossts-issues mailing list