Table of Contents

Team-Fly

---

 

	XML, Web Services, and the Data Revolution By Frank  P.  Coyle
	Table of Contents
	Appendix  B.   SOAP Version 1.2 Part 1: Messaging Framework

---

1 Introduction

1.1 Design Goals

1.2 Notational Conventions

1.3 Example of SOAP Message

1.4 SOAP Terminology

1.4.1 Protocol Concepts

1.4.2 Data Encapsulation Concepts

1.4.3 Message Sender and Receiver Concepts

2 SOAP Message Exchange Model

2.1 SOAP Nodes

2.2 SOAP Actors and SOAP Nodes

2.3 Targeting SOAP Header Blocks

2.4 Understanding SOAP Headers

2.5 Structure and Interpretation of SOAP Bodies

2.6 Processing SOAP Messages

3 Relation to XML

4 SOAP Envelope

4.1 Envelope Encoding and Versioning

4.1.1 SOAP encodingStyle Attribute

4.1.2 Envelope Versioning Model

4.2 SOAP Header

4.2.1 Use of Header Attributes

4.2.2 SOAP actor Attribute

4.2.3 SOAP mustUnderstand Attribute

4.3 SOAP Body

4.4 SOAP Fault

4.4.1 SOAP faultcode Element

4.4.2 SOAP faultstring Element

4.4.3 SOAP faultactor Element

4.4.4 SOAP detail Element

4.4.5 SOAP Fault Codes

4.4.6 MustUnderstand Faults

5 SOAP Protocol Binding Framework

5.1 Introduction

5.2 Goals of the Binding Framework

5.3 Binding Framework

5.4 Binding to Application-Specific Protocols

5.5 Security Considerations

6 Use of URIs in SOAP

7 References

7.1 Normative References

7.2 Informative References

Appendices

A Version Transition From SOAP/1.1 to SOAP Version 1.2

B Acknowledgements (Non-Normative)

C Part 1 Change Log (Non-Normative)

C.1 SOAP Specification Changes

C.2 XML Schema Changes

---

Team-Fly

Top