com.arjuna.mwlabs.wst11.at.remote

Class TransactionManagerImple

java.lang.Object

com.arjuna.mw.wst11.TransactionManager

com.arjuna.mwlabs.wst11.at.remote.TransactionManagerImple

public class TransactionManagerImple
extends TransactionManager

This is the interface that the core exposes in order to allow different types of participants to be enrolled. The messaging layer continues to work in terms of the registrar, but internally we map to one of these methods.

Constructor Summary

Constructors

Constructor and Description
TransactionManagerImple()

Method Summary

Methods

Modifier and Type	Method and Description
TxContext	currentTransaction() The currentTransaction method returns the TxContext for the current transaction, or null if there is none.
void	enlistForDurableTwoPhase(Durable2PCParticipant tpp, String id) Enlist the specified participant with current transaction such that it will participate in the 2PC protocol; a unique identifier for the participant is also required.
void	enlistForVolatileTwoPhase(Volatile2PCParticipant tpp, String id) Enlist the specified participant with current transaction such that it will participate in the Volatile 2PC protocol; a unique identifier for the participant is also required.
int	replay()
void	resume(TxContext tx) The resume method can be used to (re-)associate a thread with a transaction(s) via its TxContext.
TxContext	suspend() A thread of control may require periods of non-transactionality so that it may perform work that is not associated with a specific transaction.

Methods inherited from class com.arjuna.mw.wst11.TransactionManager

getTransactionManager, setTransactionManager

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

TransactionManagerImple

public TransactionManagerImple()

Method Detail

enlistForDurableTwoPhase

public void enlistForDurableTwoPhase(Durable2PCParticipant tpp,
                            String id)
                              throws WrongStateException,
                                     UnknownTransactionException,
                                     SystemException

Description copied from class: TransactionManager

Enlist the specified participant with current transaction such that it will participate in the 2PC protocol; a unique identifier for the participant is also required. If there is no transaction associated with the invoking thread then the UnknownTransactionException exception is thrown. If the coordinator already has a participant enrolled with the same identifier, then AlreadyRegisteredException will be thrown. If the transaction is not in a state where participants can be enrolled (e.g., it is terminating) then WrongStateException will be thrown.

Specified by:

enlistForDurableTwoPhase in class TransactionManager

Throws:

WrongStateException

UnknownTransactionException

SystemException

enlistForVolatileTwoPhase

public void enlistForVolatileTwoPhase(Volatile2PCParticipant tpp,
                             String id)
                               throws WrongStateException,
                                      UnknownTransactionException,
                                      SystemException

Description copied from class: TransactionManager

Enlist the specified participant with current transaction such that it will participate in the Volatile 2PC protocol; a unique identifier for the participant is also required. If there is no transaction associated with the invoking thread then the UnknownTransactionException exception is thrown. If the coordinator already has a participant enrolled with the same identifier, then AlreadyRegisteredException will be thrown. If the transaction is not in a state where participants can be enrolled (e.g., it is terminating) then WrongStateException will be thrown.

Specified by:

enlistForVolatileTwoPhase in class TransactionManager

Throws:

WrongStateException

UnknownTransactionException

SystemException

replay

public int replay()
           throws SystemException

Specified by:

replay in class TransactionManager

Throws:

SystemException

suspend

public TxContext suspend()
                  throws SystemException

Description copied from class: TransactionManager

A thread of control may require periods of non-transactionality so that it may perform work that is not associated with a specific transaction. In order to do this it is necessary to disassociate the thread from any transactions. The suspend method accomplishes this, returning a TxContext instance, which is a handle on the transaction. The thread is then no longer associated with any transaction.

Specified by:

suspend in class TransactionManager

Throws:

SystemException

resume

public void resume(TxContext tx)
            throws UnknownTransactionException,
                   SystemException

Description copied from class: TransactionManager

The resume method can be used to (re-)associate a thread with a transaction(s) via its TxContext. Prior to association, the thread is disassociated with any transaction(s) with which it may be currently associated. If the TxContext is null, then the thread is associated with no transaction. The UnknownTransactionException exception is thrown if the transaction that the TxContext refers to is invalid in the scope of the invoking thread.

Specified by:

resume in class TransactionManager

Throws:

UnknownTransactionException

SystemException

currentTransaction

public TxContext currentTransaction()
                             throws SystemException

Description copied from class: TransactionManager

The currentTransaction method returns the TxContext for the current transaction, or null if there is none. Unlike suspend, this method does not disassociate the current thread from the transaction(s). This can be used to enable multiple threads to execute within the scope of the same transaction.

Specified by:

currentTransaction in class TransactionManager

Throws:

SystemException