[jbossts-issues] [JBoss JIRA] (JBTM-2864) Add more tests for the JTS implementation of ExtendedJBossXATerminator

Michael Musgrove (JIRA) issues at jboss.org
Fri Mar 10 12:00:01 EST 2017

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

Michael Musgrove closed JBTM-2864.
    Fix Version/s:     (was: 5.later)
       Resolution: Rejected

The untested interface method (which were added for the EJB subsystem) have  tests have been deprecated in favour of using WFTC. PR https://github.com/jbosstm/jboss-transaction-spi/pull/23 added the deprecation whilst fixing https://issues.jboss.org/browse/WFLY-8275 

> Add more tests for the JTS implementation of ExtendedJBossXATerminator
> ----------------------------------------------------------------------
>                 Key: JBTM-2864
>                 URL: https://issues.jboss.org/browse/JBTM-2864
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTS
>    Affects Versions: 5.5.3.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
> ExtendedJBossXATerminator is our (extended) SPI interface for importing transactions and it has both JTA and JTS implementations. It is used by EJB in JTA mode which will be fully exercising the interface in JTA mode. However, we only test a subset of the interface in JTS mode (see com.arjuna.ats.jta.distributed.SimpleIsolatedServers) and these need extending to cover all of the methods.
> Note that at least one of the methods is known not to produce the correct result, namely
> {quote}
>    public Transaction getTransaction(Xid xid) throws XAException
> {quote}
> because the implementation uses XATxConverter to lookup the transaction but  XATxConverter uses a different Xid format id from the one used by JTS so it will return null (instead of the transaction corresponding to the input xid).

This message was sent by Atlassian JIRA

More information about the jbossts-issues mailing list