Service
will either implement TransactionParticipant
directly, or use some proxy as their participant. Classes that implement TransactionParticipant
must also implement Serializable
. Note that the general model assumes that Service
s will use each other during a transaction. For instance, most Service
s will use the DataService
to persist data. However once the transaction begins to prepare or is aborted (i.e., once any of the methods defined here are called on a participant), a Service
may not interact with any other Service
in the context of that transaction. Doing so results in unspecified behavior.
This interface does not specify how transaction participants learn the outcome of prepared transactions following a crash. Doing so requires a separate interaction between the participant and the transaction coordinator that is not specified by this interface. Without that additional communication, this interface is sufficient to support transactions with at most one durable transaction participant. @see NonDurableTransactionParticipant
TransactionManager
interface, this interface allows a two-phase commit protocol to be used between objects in a distributed system.
@author Sun Microsystems, Inc.
@see TransactionManager
@see NestableTransactionManager
@see ServerTransaction
@since 1.0
|
|
|
|