Database Reference
In-Depth Information
• Creating and formatting
CoordinationContext
that contains registration in-
formation, which is mandatory for all participants
• Establishing a coordination protocol based on
CoordinationContext
, and
the ways of distributing this context between participants
• Establishing a registration protocol
CoordinationContext
in the header of a SOAP message can be seen in the follow-
ing code snippet:
<wscoor:CoordinationContext>
<wsu:Expires>2014-03-21T00:00:00.0000000-05:00</wsu:Expires>
<wsu:Identifier>
uuid:0d13748c-7a09-8520-a911-17c73f09ac82
</wsu:Identifier>
<wscoor:CoordinationType>
http://schemas.xmlsoap.org/ws/2003/09/wsat
</wscoor:CoordinationType>
<wscoor:RegistrationService>
<wsa:Address>
http://erikredshipping.com/
ShcheduleCoordinationService/RegistrationCoordinator
</wsa:Address>
<wsa:ReferenceParameters >
....
<refApp:App1> ... </refApp:App1>
<refApp:App2> ... </refApp:App2>
....
</wsa:ReferenceParameters >
</wscoor:RegistrationService>
</wscoor:CoordinationContext>
The
WS-Coordination
specification is the foundation for other specifications, setting
the standards for complex coordinated activities:
WS-AtomicTransaction
and
WS-
BusinessActivity
. Both of these define a type of agreement coordination that ad-
dresses the needs of complementary classes of activities, ACID- and BASE-type require-
ments, as discussed later in this chapter.
Search WWH ::
Custom Search