Client applications and EAServer components marked as component-managed can now create, control, and obtain information about EAServer transactions using the CORBACurrent context service object, which provides most of the methods defined for the CORBA Current interface.
The CORBACurrent service object can be used by clients and components to manage transactions in a server that is running the new two-phase commit transaction coordinator (OTS/XA). CORBACurrent functions let the client or component thread begin a transaction and associate it with the calling thread and subsequently commit or roll back the transaction. Additional functions provide the ability to suspend and resume the transaction, set a timeout period after which the transaction is rolled back, and get information about the state of the transaction.
New or changed functions