Database Reference
In-Depth Information
The WSDL Message Exchange Patterns ( MEPs ) 2.0 are as follows:
• The in-out pattern , which is the standard request-response operation. This is the
most common pattern.
• The out-in pattern , where a service provider initiates the interchange.
• The in-only pattern , which is the regular fire-and-forget MEP.
• The out-only pattern , which is the reverse of the in-only pattern.
• The robust in-only pattern is similar to the previous one, but it comes with the
capability to provide the fault response message back if there is an error.
• The robust out-only pattern is similar to the out-only pattern, but it provides the
optional fault message.
• The in-optional-out pattern is similar to the in-out pattern, but here, the re-
sponse message is optional. This pattern also supports the generation of a fault
message.
• The out-optional-in pattern is the reverse of the in-optional-out pattern, where
the incoming message is optional. Here, generation of a fault message is suppor-
ted.
We will touch upon some of these MEPs later, discussing the WS-* specification's
roadmap.
WS-Addressing
The details of WS-Addressing are as shown in the following table:
Authority
Primarily addresses
Latest release
W3C
Loose Coupling and Composability http://www.w3.org/Submission/ws-addressing/
This standard is the keystone for the whole WS-* stack, as all other standards are actively
using it. It provides a neutral way of distributing messages. The SOAP header is the place-
holder for all key elements, and they are presented in the following table:
wsa: Element
Description
wsa:MessageID
This property presents the ID of a message that can be used to uniquely identify a message.
This property provides the destination URI, and it indicates where the message will be sent to. If not spe-
cified, the destination defaults to http://www.w3.org/2005/08/addressing/anonymous .
wsa:To
Search WWH ::




Custom Search