What Is SOAP RPC Presentation?

This section describes what is SOAP RPC Presentation and how to represent RPC (Remote Procedure Call) with SOAP messages.

SOAP RPC Presentation is an extension of the SOAP framework specification that defines how RPC (Remote Procedure Call) requests and responses should be presented by SOAP messages.

As programmers, we all understand that the following issues are involved to carry out a remote procedure call:

SOAP RPC Presentation defines the following rules to resolved the issues listed above:

1. The target system should be mapped as the target SOAP node, which should represented by a URI.

2. The nature of the procedure should be reviewed to see if it can be carried by other simpler SOAP extensions like SOAP Web Method Feature. See other sections of this book for detail information on other SOAP extensions.

3. The procedure name should be reviewed. If the nature of the procedure is a request for information retrieval, and the procedure name contains resource identifications that are needed to retrieve information, the target SOAP node URI should be extended to include the resource identification parts of the procedure name.

4. Input parameters of the procedure should also be reviewed. If the nature of the procedure is a request for information retrieval, and some input parameters represent resource identifications that are needed to retrieve information, the target SOAP node URI should be extended to include those input parameters.

5. If the nature of the procedure is a request for information retrieval, and the procedure name and input parameters can be entirely represented in the target SOAP node URI, this RPC invocation should be carried as a Web method defined in the SOAP Web Method Feature specification.

6. If a RPC can not be carried out as a Web method, it should be invoked by as SOAP message with a SOAP body element. The body element should use SOAP encoding and contains a single "struct" node representing the procedure name. All input parameters should be represented as outbound edges originated from this node.

7. The target SOAP node should always return a SOAP message with a SOAP body element. The body element should use SOAP encoding and contains a single "struct" node with any label. This node should have on outbound edge labeled as "result" representing the RPC return value.

8. If there are any output parameters, they should be represented as outbound edges originated from the node described in rule #7.

9. SOAP header blocks are optional in RPC invocation and response SOAP messages.

Note that SOAP RPC Presentation specification does not define how the communication should be carried out. Protocol binding specification is totally independent of SOAP RPC Presentation specification.

Last update: 2007.

Table of Contents

 About This Book

 Introduction to Web Service

 Introduction to SOAP (Simple Object Access Protocol)

 SOAP Message Structure

 SOAP Message Transmission and Processing

 SOAP Data Model

 SOAP Encoding

SOAP RPC Presentation

What Is SOAP RPC Presentation?

 Using Web Methods to Invoke RPC

 Using SOAP Messages to Invoke RPC

 RPC Response Messages

 SOAP Properties Model

 SOAP Message Exchange Patterns

 SOAP HTTP Binding

 SOAP Perl Implementations

 SOAP PHP Implementations

 SOAP Java Implementations

 Perl SOAP::Lite - SOAP Server-Client Communication Module

 Perl Socket Test Program for HTTP and SOAP

 Perl SOAP::Lite for GetSpeech SOAP 1.1 Web Service

 Perl SOAP::Lite 0.710 for SOAP 1.2 Web Services

 Perl SOAP::Lite 0.710 for WSDL

 PHP SOAP Extension Client Programs

 PHP SOAP Extension Server Programs

 Java Socket and HttpURLConnection for SOAP

 SAAJ - SOAP with Attachments API for Java

 SoapUI - SOAP Web Service Testing Tool

 WS-Security - SOAP Message Security Extension

 WS-Security X.509 Certificate Token

 Web Services and SOAP Terminology

 References

 PDF Printing Version