]
Mark Little commented on JBTM-2642:
-----------------------------------
Our version was based on the initial draft of 1.2 and then the final version. However, we
had some ifdefs in the original file (a template file) so we could support different
versions due to compliance issues with ORBs. It's possible the ifdef locations
produced a different ordering or that there were changes in the standards we didn't
track.
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.