]
Tom Jenkinson commented on JBTM-2642:
-------------------------------------
I set 6.later as it is likely a big change, we can bring it back down to 5.later if
necessary with a config option.
Interoperability issues with ArjunaJTS CosTransactions idl
----------------------------------------------------------
Key: JBTM-2642
URL:
https://issues.jboss.org/browse/JBTM-2642
Project: JBoss Transaction Manager
Issue Type: Bug
Components: JTS
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 6.later
The copy of CosTransactions.idl in our source tree does not match any of the OTS spec
versions, in partciular the enum ordering of Status values is different so we get the
wrong status when asking foreign application servers for the status of a transaction.
I checked versions 1.0 and 1.1 (
http://www.omg.org/spec/OTS/) and versions 1.3 and 1.4
(
http://www.omg.org/spec/TRANS/), I could not locate version 1.2. The idl used by other
application servers seems to match versions 1.3 and 1.4:
{code}
enum Status {
StatusActive,
StatusMarkedRollback,
StatusPrepared,
StatusCommitted,
StatusRolledBack,
StatusUnknown,
StatusNoTransaction,
StatusPreparing,
StatusCommitting,
StatusRollingBack
};
{code}
whereas we are using
{code}
enum Status { StatusActive, StatusMarkedRollback, StatusPrepared,
StatusCommitted, StatusRolledBack, StatusUnknown,
StatusPreparing, StatusCommitting, StatusRollingBack,
StatusNoTransaction };
{code}
Notice that the enum position of StatusNoTransaction is different.