Quality of Service - Java SOA - page 825

9. Missing messages are re-sent by the source. They include the same message number and
sequence ID as the original messages so that the destination can recognize them.
10. The WS-RM destination receives any re-sent messages and acknowledges this.
11. The WS-RM source asks for acknowledgment that the messages were all received prop-
erly using an <AckRequested> header.
12. The WS-RM source receives the acknowledgment from the WS-RM destination, and
sends a <TerminateSequence> header to indicate that it's done sending messages for this
sequence. The WS-RM source cleans up any resources associated with the sequence.
13. The WS-RM destination receives the terminate sequence message and reclaims the re-
sources associated with managing the sequence.
WS-ReliableMessaging and WS-Addressing exchange
Beware that WS-RM adds considerable bloat to your messages. To illustrate the various parts
of the WS-RM infrastructure at work, Example 13-1 is a request that is generated to accom-
modate the need for WS-ReliableMessaging and WS-Addressing.
Example13-1.WS-RM request message
---[HTTP request]---
SOAPAction: "http://soacookbook.com/sigcap/get"
Accept: text/xml, multipart/related,
text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Content-Type: multipart/related;
start="<rootpart*[e-mail]>";
type="application/
xop+xml";boundary="uuid:c19f6849-27ee-473a-b02c-5e7b1130818a";
start-info="text/xml"
--uuid:c19f6849-27ee-473a-b02c-5e7b1130818a
Content-Id:
<rootpart*[e-mail]>
Content-Type: application/xop+xml;charset=utf-8;type="text/xml"
Content-Transfer-Encoding: binary
<?xml version='1.0' encoding='UTF-8'?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Header>
<To xmlns="http://www.w3.org/2005/08/addressing">
http://localhost:8080/sigcap-ws-1.1.0/SigCapService
</To>
<Action xmlns="http://www.w3.org/2005/08/addressing">
http://soacookbook.com/sigcap/get
</Action>