SOAP Version 1.2

 

 

SOAP Version 1.2W3C Working ing Draft 9 July 2001

English version:

Http://www.w3.org/TR/2001/WD-soap12-20010709/

English version:

Http://www.w3.org/TR/soap12/

Edit the English version:

Martin Gudgin (DevelopMentor)

Marc Hadley (Sun Microsystems)

Jean-Jacques Moreau (Canon)

Henrik Frystyk Nielsen (Microsoft Corp .)

　

Chinese version:

Http://www.uddi-china.org/pubs/misc/soap12.htm

Edit Chinese version:

Chai Xiaolu, Fennivel Chai (DealEasy)

Chinese version contributors:

Xu Youjun, Arthor Xu (DealEasy)

　

Copyright? 2001W3C? (MIT,INRIA,Keio), All Rights Reserved. W3CLiability,Trademark,Document useAndSoftware licensingRules apply.

Abstract

SOAP 1.2 provides a simple and lightweight mechanism for exchanging structured and typed information with XML in a loose and distributed environment. This is an XML-based protocol, which consists of four parts: an envelope (envelope) that describes the content of a message and the information framework for processing the message ), A set of encoding rules used to indicate the data types defined by the application (encoding rules), a convention used to indicate remote process calls and responses, and a binding used to exchange messages using the underlying protocol (binding) conventions. Potentially, SOAP can be bound to many other protocols. However, this document only defines that SOAP and HTTP have been bound to HTTP Extension Framework.

Status of this Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.

This is the first W3C Working Draft of the SOAP version 1.2 specification for review by W3C members and other interested parties. it has been produced by the XML Protocol Working Group (WG), which is part ofXML Protocol Activity.

The XML Protocol Working Group has, in keeping with its charter, producedSet of requirements and usage scenariosThat have been published as a Working Draft. To better evaluate SOAP/1.1 against these requirements and usage scenarios, the Working Group has producedAbstract model and a glossary of terms and conceptsUsed by the Working Group. In addition, the Working Group has producedIssues listThat describes issues and concerns raised by mapping its requirements and the XMLP abstract model against the SOAP/1.1 specification as well as issues raised on the <Xml-dist-app@w3.org& Gt; mailing list against SOAP/1.1.

The current name for this specification is SOAP version 1.2, this first Working Draft being based on SOAP/1.1 as per the Working Groups charter (see change log inAppendix D)

Comments on this document shocould be sentXmlp-comments@w3.org(Public archives). It is inappropriate to send discussion emails to this address.

Discussion of this document takes place on the public <Xml-dist-app@w3.org> Mailing list (Archives) PerEmail communication rulesInXML Protocol Working Group Charter.

This is a public W3C Working Draft. it is a draft document and may be updated, replaced, or obsoleted by other documents at any time. it is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress ". A list of all W3C technical reports can be foundHttp://www.w3.org/TR/.

Table of Contents

1. Introduction

1.1 design objectives

1.2 symbol conventions

1.3 SOAP message example

1.4 SOAP terminology

1.4.1 protocol Concept

1.4.2 Data encapsulation Concept

1.4.3 concepts of message senders and receivers

1.4.4 Data Encoding Concept

2. SOAP message exchange model

2.1 SOAP nodes

2.2 SOAP role and SOAP Node

2.3 locate SOAP Header entries

2.4 understand SOAP Header

2.5 process messages

3. Relationship with XML

4. SOAP envelope

4.1.1 attributes of SOAP encodingStyle

4.1.2 Envelope version Model

4.2 SOAP Header

4.2.1 use the Header attribute

4.2.2 SOAP actor Attribute

4.2.3 SOAP mustUnderstand Attribute

4.3 SOAP Body

4.3.1 relationship between SOAP Header and Body

4.4 SOAP errors

4.4.1 SOAP error code

4.4.2 MustUnderstand Error

5. SOAP Encoding

5.1 rules for Type encoding using XML

5.2 simple type

5.2.1 string

5.2.2 Enumeration

5.2.3 byte array

5.3 multi-state access Mark

5.4 Composite Type

5.4.1 reference of compound values and Pairs

5.4.2 Array

5.4.2.1 partial transmission array

5.4.2.2 sparse array

5.4.3 common composite types

5.5 Default Value

5.6 SOAP root attributes

6. Use SOAP in HTTP

6.1 soap http Request

6.1.1 SOAPAction field in HTTP Header

6.2 soap http Response

6.3 HTTP extension framework

6.4 soap http example

7. Use SOAP in RPC

7.1 RPC and SOAP Body

7.2 RPC and SOAP Header