This exception is raised if the FactoryFinder or the CORBAservices Naming
Service encounter an internal error during the search, with the error being
written to the user log (ULOG).
The Current interface defines methods that allow a client of the
Transaction Service to explicitly manage the association between threads
and transactions.
This member function instructs the FactoryFinder to return one application
factory object reference whose id in the key matches the method's input
factory_id.
If the client is associated with a transaction, a Control object is returned that represents the
transaction context currently associated with the client thread.
If there is a transaction associated with the client thread, this method returns a printable string
describing the transaction (specifically the XID as specified by the Open
Group).
This exception is thrown by the rollback operation on a resource to
report that a heuristic decision was made and that all relevant updates
have been committed.
A request raises this exception to report that a heuristic decision was
made, the disposition of all relevant updates is not known, and for those
updates whose disposition is known, either all have been committed or all
have been rolled back.
A request raises this exception to report that a heuristic decision was
made and that some relevant updates have been committed and others have
been rolled back.
This exception is thrown to report that a heuristic decision was made and
that some relevant updates have been committed and others have been
rolled back.
This exception is raised for the Current interface commit, rollback, and
rollback_only methods if there is no transaction associated with the
client thread.
Acquires CORBA object references for the FactoryFinder, SecurityCurrent,
TransactionCurrent, NotificationService, Tobj_SimpleEventsService,
and InterfaceRepository objects.
If the parameter is a valid object reference in the current execution environment, the client thread
becomes associated with that transaction (in place of any previous transaction).
This method modifies a state variable associated with the target object
that affects the time-out period associated with transactions created by
subsequent invocations of the begin method.
This exception is raised for the Current interface begin method if the
client already has an associated transaction and the Transaction Service
implementation does not support nested transactions.
If in a proper context with a transaction not marked ROLLEDBACK, an object is
returned that represents the transaction context currently associated with
the client thread.
The TransactionCurrent interface supports all the methods of the Current interface in the
CosTransactions module, as described in the previous section.