[
https://issues.jboss.org/browse/JBTM-2864?page=com.atlassian.jira.plugin....
]
Michael Musgrove updated JBTM-2864:
-----------------------------------
Description:
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).
was: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.
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
Fix For: 5.later
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
(v7.2.3#72005)