Database Reference
In-Depth Information
The guarantee is specified as a delivery assurance. The protocol supports the endpoints by
providing these delivery assurances. It is the responsibility of the RM source and the RM
destination to fulfill the delivery assurances or raise an error. It would be right to see the
analogy between WSRM and JMS in the Java world in terms of delivery assurance. The
key differences are that JMS is highly platform-specific with a standard API, whereas
WSRM is platform-independent by means of SOAP (and WSDL). Of course, WSRM
agents (handlers) must be implemented behind services WSDLs and also on the client side
to retransmit the message if necessary or provide the acknowledgement; however, these
agents are invisible at the service/application's interaction levels. WSRM is an extension
of SOAP, and all of its protocols are based on the concept of
sequence
. Sequence is the
number of predefined steps, shown as follows:
•
CreateSequence
•
CreateSequenceResponse
•
CloseSequence
•
CloseSequenceResponse
•
TerminateSequence
•
TerminateSequenceResponse
You can see the latest specification on the official OASIS site.
Reliable messaging in a WSDL implementation is as shown in the following code snippet:
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/
wsdl/"
xmlns:xs="http://www.w3.org/2001/
XMLSchema"
xmlns:wsa="http://www.w3.org/2005/08/
addressing"
xmlns:wsam="http://www.w3.org/2007/05/
addressing/metadata"
xmlns:rm="http://docs.oasis-open.org/
ws-rx/wsrm/200702"
xmlns:tns="http://docs.oasis-open.org/
ws-rx/wsrm/200702/wsdl"
targetNamespace="http://docs.oasis-open.org/ws-rx/wsrm/
Search WWH ::
Custom Search