Operation Message Styles

This section describes operation message styles defined in WSDL Version 2.0 Part 2: Adjuncts - RPC, IRI, and Multipart.

What Is Message Style? A Message Style defines a set of rules to be applied to an operation in an abstract interface to control its message styles. Each style is represented by a unique URI, which can be specified as the "style" attribute of an operation.

WSDL 2.0 specification (WSDL Version 2.0 Part 2: Adjuncts) provides 3 predefined styles: RPC, IRI, and Multipart.

RPC Style - Represented by URI: http://www.w3.org/ns/wsdl/style/rpc - RPC defines a set of rules to simulate an RPC (Remote Procedure Call) method.

RPC style has following main rules:

1. Only "In-Only" or "In-Out" message exchange pattern can be used with RPC style.

2. The input message (and output message, if used) must have "#element" appended to the end of the "element" attribute. For example:

  <wsdl:operation name="GetQuote" ...
    style="http://www.w3.org/ns/wsdl/style/rpc">
    <wsdl:input messageLabel="In" element="hy:GetQuote#element"/>
    <wsdl:output messageLabel="Out" element="hy:GetQuoteRes#element"/>
    ...
  </wsdl:operation>

3. The input message element name must be the same as the operation name.

4. The input and output message elements MUST both be in the same namespace.

5. The XML schema that defines the input message element (and output message element if used) has additional rules:

IRI Style - Represented by URI: http://www.w3.org/ns/wsdl/style/iri - IRI defines a set of rules according the IRI (Internationalized Resource Identifier) specification intended for HTTP GET operations.

IRI style has following main rules:

1. Only "In-Only" or "In-Out" message exchange pattern can be used with IRI style.

2. The initial message of the message exchange pattern must have "#element" appended to the end of the "element" attribute. For example:

  <wsdl:operation name="GetQuote" ...
    style="http://www.w3.org/ns/wsdl/style/iri">
    <wsdl:input messageLabel="In" element="hy:GetQuote#element"/>
    ...
  </wsdl:operation>

3. The input message element name must be the same as the operation name.

4 The XML schema that defines the element of the input message has additional rules:

Note that:

Multipart Style - Represented by URI: http://www.w3.org/ns/wsdl/style/multipart - Multipart style has following main rules:

Multipart style has following main rules:

1. The initial message of the message exchange pattern must have "#element" appended to the end of the "element" attribute. For example:

  <wsdl:operation name="GetQuote" ...
    style="http://www.w3.org/ns/wsdl/style/multipart">
    <wsdl:input messageLabel="In" element="hy:GetQuote#element"/>
    ...
  </wsdl:operation>

2 The XML schema that defines the element of the initial message has additional rules:

Note that:

Table of Contents

 About This Book

 Introduction to WSDL 2.0

 WSDL 2.0 Document Structure and Syntax

WSDL Version 2.0 Part 2: Adjuncts

 WSDL Message Exchange Patterns

 wsdlx:safe="true|false" Operation Safety

Operation Message Styles

 SOAP Binding Extension

 SOAP 1.2 Binding Rules

 WSDL 2.0 Document Examples with SOAP Binding

 Using WSDL Document in Java Apache Axis2/Java for WSDL

 Apache Woden for WSDL Documents in Java

 SoapUI - Web Service Testing Tool

 PHP SOAP Extension for WSDL

 Perl SOAP::Lite for WSDL

 Introduction to WSDL 1.1

 WSDL 1.1 Document Structure and Syntax

 WSDL 1.1 Binding Extension for SOAP 1.1

 SoapUI as WSDL 1.1 Testing Tool

 WSDL 1.1 and SOAP 1.1 Examples - Document and RPC Styles

 PHP SOAP Extension for WSDL 1.1

 Perl SOAP::Lite for WSDL 1.1

 Apache Axis2/Java for WSDL 1.1

 Using WSDL2Java to Generate Web Service Stub Classes

 WSDL 1.1 Binding Extension for SOAP 1.2

 WSDL 1.1 and SOAP 1.2 Examples - Document and RPC Styles

 SOAP 1.2 Binding - PHP, Java and Perl Clients

 Python SOAP Client: Zeep

 WSDL Related Terminologies

 Archived Tutorials

 References

 Full Version in PDF/EPUB