SOAP Routing and Message Path Modeling

This document defines a SOAP feature that represents an abstract model for SOAP attachments. It provides the basis for the creation of SOAP bindings that transmit such attachments along with a SOAP envelope, and provides for reference of those attachments from the envelope.

This document records known errors in the SOAP Version 1.2 Specification for which there are approved fixes.

SOAP [1] is a lightweight protocol that defines a method for the exchange of messages independently from the programming language and platform. For interoperability, the SOAP specification is also agnostic about possible transport protocols, though almost all existing implementations use mainly HTTP.

I have been testing out using SOAP from Tcl and have come up with the following package to provide Tcl commands for SOAP remote procedure calls. The following code demonstrates the ease of use for simple RPC calls. This is a work in progress and some parts need more work.

We're experimenting SOAP/RDF mapping tools, on the hypothesis that the SOAP Encoding Data Model and RDF's graph data model are close enough for RDF tools to be able to consume SOAP-encoded graphs, and for SOAP Encoding to serve as an alternate unstriped XML syntax for RDF.

The Request object represents a SOAP request. It contains all the information required to invoke a web service, as well as specifying what action to take when the request is complete.

For a variety of reasons, it is desirable that some web services, compliant with the SOAP HTTP Binding, can also be accessed via HTTP GET.

What is SOAP? What is not SOAP? Where is SOAP?

Journals now support SOAP. This is experimental and subject to change, though I hope that it won't change significantly, except to fix bugs and improve in various ways. There are five methods.

Once we have a SOAP message, we will probably want to send it to someone. After all, what good is a message if it never goes anywhere? The transport is the method by which a SOAP message is moved from sender to receiver. One example of a transport is HTTP, the Hypertext Transfer Protocol.

SOAP itself does not handle objects. In fact, the object in "simple object access protocol" lends itself simply to the formation of a outstanding name. Actually, SOAP was intended for RPC use and designed to convert a method's parameters from its native binary form and carry those parameters to the remote server as XML information.

This article starts with the basics of SOAP, SOAP XML model and its data types followed by the integration of SOAP functionality in .NET class library and how .NET developers can take advantages of SOAP in their applications. It also gives you an overview of SOAP tooklit and SOAP extensions and COM late binding integration with SOAP and .NET.

In SOAP, the details about the RPC are in an XML message. In our Simple SOAP Implementation example, details will be in parameters of HTTP request.

XML RPC and SOAP

A web service is a web-based software application that can be located and accessed via a set of standardized protocols and helper applications.

SOAP (Simple Object Access Protocol) has become synonymous with XML- based Web services. However, many real-world response-request-type Web services don't use SOAP; instead, they pass XML messages directly over HTTP. This article discusses these two Web service design approaches.

The recent announcement that the backers of ebXML will use the Simple Object Access Protocol (SOAP) in the proposed standard came as a surprise to some. But for those involved in the formation of ebXML, the use of SOAP is a natural progression.

Introduction to SOAP. [PDF]

What is SOAP ? [PPT]