CORBA 2.6.1 Programmer's Reference

Transaction Models (1.2.4.1)
The specification defines nested transactions. These transactions are optional and are not supported by
NSOTS.
Service Architecture: Transaction Context (1.3.2)
NSOTS does not support the transactional Dynamic Invocation Interface.
Service Architecture: Exceptions (1.3.6)
In general, NSOTS does not provide exception minor codes. However, when an exception is initiated by
Open TMF, NSOTS assigns the TMF error code to the CORBA exception minor code.
Current Interface (2.2)
For C++, NSOTS adds two operations to the Current interface:
interface Current : CORBA::Control {
void tmf_start (in long long xid);
void tmf_end ();
};
These operations control the participation of NSOTS in extant Open TMF transactions. This normally
occurs when adding CORBA features to a legacy program. See 7.13 Model Interoperability.
TransactionFactory Interface (2.3)
The TransactionFactory interface is not supported by NSOTS. Developers should design
applications around the use of the Current interface.
Coordinator Interface: get_transaction_name
(2.6.1.5.)
For C++, get_transaction_name() is implemented as a wrapper for TRANSIDTOTEXT() and
can be useful with TMFCOM for debugging.
RecoveryCoordinator Interface: replay_completion
(2.7.1)
During recovery replay_completion() might incorrectly return StatusUnknown. The invoking