Java Doc for ATCoordinator.java in » 6.0-JDK-Modules-com.sun » wsit » com » sun » xml » ws » tx » at » Java Source Code / Java DocumentationJava Source Code and Java Documentation
Atomic Transaction Coordinator
Coordinator States: NONE, ACTIVE, Volatile2PCPrepare, Durable2PCPrepare, Committing, Aborting
Relationship between ATCoordinator and Java Transaction Manager.
ATCoordinator is registered as an XAResource with Java Transaction Manager.
This enables Java Transaction Manager to be root transaction manager that
for ATCoordinator durable 2pc participants. ATCoordinator registers for
Transaction Synchronization if it has volatile participants. This enables
volatile participants to be prepared BEFORE durable 2pc participants are prepared.
Coordination Context expires specifies the period, measured from
the point in time at which the context was first created or received, after which a
transaction MAY be terminated solely due to its length of operation.
From that point forward, the coordinator MAY elect to unilaterally roll back the transaction,
so long as it has not made a commit decision.
author: Ryan.Shoemaker@Sun.COM author: Joe.Fialli@Sun.COM version: $Revision: 1.19 $ since: 1.0
initiateDurablePrepare() TODO: Each PREPARED/READONLY Volatile ATParticipant should check if it is time to start
the durable 2PC phase by calling this method.
initiateVolatilePrepare() Send 2PC prepare to all volatile participants
Volatile 2PC prepare constraint from 2004 WS-AT, section 3.3.1
the root coordinator begins the prepare phase of all participants registered for the Volatile 2PC protocol.
All participants registered for this protocol must respond before a Prepare is issued to a
participant registered for Durable 2PC.
Construct a new Coordinator object from the specified context and soap request.
This method is an entry point for the Activation service's createCoordinationContext
operation. This entry point probably won't be used much, or not at all if we choose
not to publish the operation (which is optional in the WS-Coordination spec).
Parameters: context - The coordination context Parameters: request - The soap request
Construct a new Coordinator object from the specified context.
This constructor will be the main entry point for activity within the
AppServer.
Parameters: context - The coordination context
Register this with TransactionSynchronizationRegistery. This should get called by JTS
transaction system before 2PC Participants and XAResources are prepared.
Get the registrant with the specified id or null if it does not exist.
Parameters: id - the registrant id the Registrant object or null if the id does not exist
Send 2PC prepare to all volatile participants
Volatile 2PC prepare constraint from 2004 WS-AT, section 3.3.1
the root coordinator begins the prepare phase of all participants registered for the Volatile 2PC protocol.
All participants registered for this protocol must respond before a Prepare is issued to a
participant registered for Durable 2PC. Further participants may register with the coordinator until the
coordinator issues a Prepare to any durable participant.