org.omg.CosTransactions

Class ControlPOA

public abstract class ControlPOA extends Servant implements ControlOperations, InvokeHandler

The Control interface allows a program to explicitly manage or propagate a transaction context. An object supporting the Control interface is implicitly associated with one specific transaction. The Control interface defines two operations, get_terminator and get_coordinator. The get_terminator operation returns a Terminator object, which supports operations to end the transaction. The get_coordinator operation returns a Coordinator object, which supports operations needed by resources to participate in the transaction. The two objects support operations that are typically performed by different parties. Providing two objects allows each set of operations to be made available only to the parties that require those operations. A Control object for a transaction is obtained using the operations defined by the TransactionFactory interface or the create_subtransaction operation defined by the Coordinator interface. It is possible to obtain a Control object for the current transaction (associated with a thread) using the get_control or suspend operations defined by the Current interface. (These two operations return a null object reference if there is no current transaction.) An implementation of the Transaction Service may restrict the ability for the Control object to be transmitted to or used in other execution environments; at a minimum, it can be used within a single thread.
Method Summary
String[]_all_interfaces(POA poa, byte[] objectId)
OutputStream_invoke(String opName, InputStream _is, ResponseHandler handler)
Control_this()
Control_this(ORB orb)

Method Detail

_all_interfaces

public String[] _all_interfaces(POA poa, byte[] objectId)

_invoke

public final OutputStream _invoke(String opName, InputStream _is, ResponseHandler handler)

_this

public Control _this()

_this

public Control _this(ORB orb)