SOAP VERSION 1.2 Chinese Manual 1

SOAP VERSION 1.2

W3C Working Draft 9 July 2001

English version:

Http://www.w3.org/tr/2001/wd-soap12-20010709/

English version of the final version:

http://www.w3.org/tr/soap12/

English Edition Editor:

Martin gudgin (developor)

Marc Hadley (Sun Microsystems)

Jean-Jacques moreau (Canon)

Henrik Frystyk Nielsen (Microsoft Corp.)

Chinese Version:

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

Chinese Edition Editor:

Fennivel Chai (Dealeasy)

Chinese version contributor:

Xu Youjun, ARTHOR XU (de Aleasy)

Copyright © 2001 W3C® (MIT, INRIA, KEIO), All Rights Reserved. W3C Liability, Trademark, Document Use and Software Licensing Rules Apply.

Abstract

SOAP 1.2 provides a simple and lightweight mechanism for exchanging structured and type information using XML pairs in a loose, distributed environment. This is an XML-based protocol, which consists of four parts: an envelope as an envelope that describes the content frame of the message and how to handle the message, a set of encoding rules for indicating the application defined data type ( Encoding Rules), a binding convention for indicating remote procedure calls and returns and a binding of messaging using the underlying protocol. Potentially, SOAP can be used to bind a lot of other protocols; however, in this document, only SOAP and HTTP have been bound to HTTP EXTENSION FRAMEWORK.

Status of this document

...........................................................................................................................................................

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 of the XML Protocol Activity.

The XML Protocol Protocol Working Group has, in keeping with its charter, produced a set of requirements and usage scenarios that have been published as a Working Draft. To better evaluate SOAP / 1.1 against these requirements and usage scenarios, the Working Group has produced an abstract model and a glossary of terms and concepts used by the Working Group. In addition, the Working Group has produced an issues list that 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 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 Group's charter ( See Change Log in appendix d)

Comments on this document Should Be Sent To Xmlp-Comments@w3.org (public archives). It is inapprids to called this address.

Discussion of this Document Takes Place on the public Mailing List (Archives) Per The Email Communication Rules in The XML 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 ". A List of all w3c technical reports can be found at http://www.w3.org/tr/.

Table of contents

1 Introduction

1.1 Design Goal

1.2 symbol agreement

1.3 SOAP Message Example

1.4 SOAP terminology

1.4.1 protocol concept

1.4.2 Data Packaging Concept

1.4.3 Messaging Manager and Receiver Concept

1.4.4 Data Coding Concept

2. SOAP message exchange model

2.1 SOAP Node

2.2 SOAP role with soap

Node

2.3 Positioning the SOAP Header entry

2.4 Understand SOAP Header

2.5 processing message

3. Relationship with XML

4. SOAP Envelope 4.1.1 SOAP ENCODINGSTYLE attribute

4.1.2 ENVELOPE version model

4.2 SOAP HEADER

4.2.1 Using Header Attributes

4.2.2 SOAP Actor

Attributes

4.2.3 SOAP MUSTUNDERSTAND

Attributes

4.3 SOAP BODY

4.3.1 Relationship between SOAP HEADER and BODY

4.4 SOAP error

4.4.1 SOAP error code

4.4.2 Mustunderstand Error

5. SOAP encoding

5.1 Rule for type encoding using XML

5.2 Simple Type

5.2.1 String

5.2.2 enumeration

5.2.3 byte arrays

5.3 Polymorphism

5.4 composite type

5.4.1 Quote for composite values

5.4.2 array

5.4.2.1 Partial transmission array

5.4.2.2 Sparse array

5.4.3 Universal Composite Type

5.5 default value

5.6 SOAP root properties

6. Use SOAP in HTTP

6.1 SOAP HTTP Request

6.1.1 SoapAction fields 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

8. Considering the safety mechanism

9. References

9.1. NORMATIVE REFERENCES

9.2. Informative References

A. SOAP Envelope Examples

A.1 Sample Encoding of Call Requests

A.2 Sample ENCODING OF RESPONSE

B. Acknowledgements

C. Version Transition from SOAP / 1.1 To SOAP / 1.2

D. Change log

D.1 SOAP Specification Changes

D.2 XML Schema Changes