org.omg.CosTransactions
Interface TerminatorOperations

All Known Subinterfaces:
Terminator
All Known Implementing Classes:
_TerminatorStub, SubTransTerminator, Terminator, TerminatorPOA, TerminatorPOATie

public interface TerminatorOperations

The Terminator interface supports operations to commit or rollback a transaction. Typically, these operations are used by the transaction originator.


Method Summary
 void commit(boolean report_heuristics)
          If the transaction has not been marked rollback only, and all of the participants in the transaction agree to commit, the transaction is committed and the operation terminates normally.
 void rollback()
          The transaction is rolled back.
 

Method Detail

commit

void commit(boolean report_heuristics)
            throws HeuristicMixed,
                   HeuristicHazard
If the transaction has not been marked rollback only, and all of the participants in the transaction agree to commit, the transaction is committed and the operation terminates normally. Otherwise, the transaction is rolled back (as described below) and the TRANSACTION_ROLLEDBACK standard exception is raised. If the report_heuristics parameter is true, the Transaction Service will report inconsistent or possibly inconsistent outcomes using the HeuristicMixed and HeuristicHazard exceptions. A Transaction Service implementation may optionally use the Event Service to report heuristic decisions. The commit operation may rollback the transaction if there are subtransactions of the transaction that have not themselves been committed or rolled back or if there are existing or potential activities associated with the transaction that have not completed. The nature and extent of such error checking is implementation-dependent. When a top-level transaction is committed, all changes to recoverable objects made in the scope of this transaction are made permanent and visible to other transactions or clients. When a subtransaction is committed, the changes are made visible to other related transactions as appropriate to the degree of isolation enforced by the resources.

Throws:
HeuristicMixed
HeuristicHazard

rollback

void rollback()
The transaction is rolled back. When a transaction is rolled back, all changes to recoverable objects made in the scope of this transaction (including changes made by descendant transactions) are rolled back. All resources locked by the transaction are made available to other transactions as appropriate to the degree of isolation enforced by the resources.