- XML Reference Guide
- Overview
- What Is XML?
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Table of Contents
- The Document Object Model
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- DOM and Java
- Informit Articles and Sample Chapters
- Books and e-Books
- Implementations
- DOM and JavaScript
- Using a Repeater
- Repeaters and XML
- Repeater Resources
- DOM and .NET
- Informit Articles and Sample Chapters
- Books and e-Books
- Documentation and Downloads
- DOM and C++
- DOM and C++ Resources
- DOM and Perl
- DOM and Perl Resources
- DOM and PHP
- DOM and PHP Resources
- DOM Level 3
- DOM Level 3 Core
- DOM Level 3 Load and Save
- DOM Level 3 XPath
- DOM Level 3 Validation
- Informit Articles and Sample Chapters
- Books and e-Books
- Documentation and Implementations
- The Simple API for XML (SAX)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- SAX and Java
- Informit Articles and Sample Chapters
- Books and e-Books
- SAX and .NET
- Informit Articles and Sample Chapters
- SAX and Perl
- SAX and Perl Resources
- SAX and PHP
- SAX and PHP Resources
- Validation
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Document Type Definitions (DTDs)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XML Schemas
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- RELAX NG
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Schematron
- Official Documentation and Implementations
- Validation in Applications
- Informit Articles and Sample Chapters
- Books and e-Books
- XSL Transformations (XSLT)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XSLT in Java
- Java in XSLT Resources
- XSLT and RSS in .NET
- XSLT and RSS in .NET Resources
- XSL-FO
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XPath
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XML Base
- Informit Articles and Sample Chapters
- Official Documentation
- XHTML
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XHTML 2.0
- Documentation
- Cascading Style Sheets
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XUL
- XUL References
- XML Events
- XML Events Resources
- XML Data Binding
- Informit Articles and Sample Chapters
- Books and e-Books
- Specifications
- Implementations
- XML and Databases
- Informit Articles and Sample Chapters
- Books and e-Books
- Online Resources
- Official Documentation
- SQL Server and FOR XML
- Informit Articles and Sample Chapters
- Books and e-Books
- Documentation and Implementations
- Service Oriented Architecture
- Web Services
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Creating a Perl Web Service Client
- SOAP::Lite
- Amazon Web Services
- Creating the Movable Type Plug-in
- Perl, Amazon, and Movable Type Resources
- Apache Axis2
- REST
- REST Resources
- SOAP
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- SOAP and Java
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- WSDL
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- UDDI
- UDDI Resources
- XML-RPC
- XML-RPC in PHP
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Ajax
- Asynchronous Javascript
- Client-side XSLT
- SAJAX and PHP
- Ajax Resources
- JSON
- Ruby on Rails
- Creating Objects
- Ruby Basics: Arrays and Other Sundry Bits
- Ruby Basics: Iterators and Persistence
- Starting on the Rails
- Rails and Databases
- Rails: Ajax and Partials
- Rails Resources
- Web Services Security
- Web Services Security Resources
- SAML
- Informit Articles and Sample Chapters
- Books and e-Books
- Specification and Implementation
- XML Digital Signatures
- XML Digital Signatures Resources
- XML Key Management Services
- Resources for XML Key Management Services
- Internationalization
- Resources
- Grid Computing
- Grid Resources
- Web Services Resource Framework
- Web Services Resource Framework Resources
- WS-Addressing
- WS-Addressing Resources
- WS-Notifications
- New Languages: XML in Use
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Google Web Toolkit
- GWT Basic Interactivity
- Google Sitemaps
- Google Sitemaps Resources
- Accessibility
- Web Accessibility
- XML Accessibility
- Accessibility Resources
- The Semantic Web
- Defining a New Ontology
- OWL: Web Ontology Language
- Semantic Web Resources
- Google Base
- Microformats
- StructuredBlogging
- Live Clipboard
- WML
- XHTML-MP
- WML Resources
- Google Web Services
- Google Web Services API
- Google Web Services Resources
- The Yahoo! Web Services Interface
- Yahoo! Web Services and PHP
- Yahoo! Web Services Resources
- eBay REST API
- WordML
- WordML Part 2: Lists
- WordML Part 3: Tables
- WordML Resources
- DocBook
- Articles
- Books and e-Books
- Official Documentation and Implementations
- XML Query
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- XForms
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Resource Description Framework (RDF)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Topic Maps
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation, Implementations, and Other Resources
- Rich Site Summary (RSS)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- Simple Sharing Extensions (SSE)
- Atom
- Podcasting
- Podcasting Resources
- Scalable Vector Graphics (SVG)
- Informit Articles and Sample Chapters
- Books and e-Books
- Official Documentation
- OPML
- OPML Resources
- Summary
- Projects
- JavaScript TimeTracker: JSON and PHP
- The Javascript Timetracker
- Refactoring to Javascript Objects
- Creating the Yahoo! Widget
- Web Mashup
- Google Maps
- Indeed Mashup
- Mashup Part 3: Putting It All Together
- Additional Resources
- Frequently Asked Questions About XML
- What's XML, and why should I use it?
- What's a well-formed document?
- What's the difference between XML and HTML?
- What's the difference between HTML and XHTML?
- Can I use XML in a browser?
- Should I use elements or attributes for my document?
- What's a namespace?
- Where can I get an XML parser?
- What's the difference between a well-formed document and a valid document?
- What's a validating parser?
- Should I use DOM or SAX for my application?
- How can I stop a SAX parser before it has parsed the entire document?
- 2005 Predictions
- 2006 Predictions
- Nick's Book Picks
Technically speaking, "Web Services" doesn't refer to any particular form of message being sent over the Internet, but one of the most common (and the way things are going, the most standardized) type of messages is the SOAP message. Early versions of SOAP stood for Simple Object Access Protocol, but with Version 1.2, currently a Candidate Recommendation at the W3C, the acronym has been dropped. Whatever you want to call it, however, it pays to understand how SOAP messages are constructed.
Consider the example of a Web service in which a client can place an order for hyperdrive engines. The message has to contain all of the information the engine company needs to process the order:
<?xml version='1.0' ?> <env:Envelope xmlns:env="http://www.w3.org/2002/12/soap-envelope"> <env:Header> <orderinfo:customer xmlns:orderinfo="http://www.example.com/enginesinc/customers"> <orderinfo:custId>DWDD39928</orderinfo:custId> <orderinfo:payMethod>PO</orderinfo:payMethod> <orderinfo:refNumber>PPSI998</orderinfo:refNumber> </orderinfo:customer> </env:Header> <env:Body> <order:action type="add" xmlns:order="http://www.example.com/enginesinc/orders"> <order:itemId>XJ443</order:itemId> <order:itemPrice>383902</order:itemPrice> <order:itemQty>3</order:itemQty> </order:action> </env:Body> </env:Envelope>
Here we have XML data in three different namespaces. First, we have the SOAP message itself, consisting of an Envelope element containing a Body and an optional Header. The structure of the message itself is up to you and will be determined by the application that you build to process it, but in general the Header element contains information about the request, while the Body contains the message itself, also known as the payload.
The SOAP specification doesn't mandate any particular structure within the Header or Body elements; that's up to your application. What it does is specify attributes that control the way the message is treated by any system through which it passes. For example, A SOAP message will typically pass through one or more intermediaries between its initial departure from the ultimate sender and its receipt by the ultimate receiver. Each of these intermediaries can process the message, if the role is set for it.
For example, we could set up the message so that the marketing department gets notification that one of their advertisements has actually resulted in a sale by adding an element to the Header:
<?xml version='1.0' ?> <env:Envelope xmlns:env="http://www.w3.org/2002/12/soap-envelope"> <env:Header> <marketing:activity xmlns:marketing="http://www.example.com/enginesinc/marketing" env:role="http://www.w3.org/2002/12/soap-envelope/role/next" env:mustUnderstand="true"> <marketing:source>HyperDrive Today</marketing:source> </marketing:activity> <orderinfo:customer xmlns:orderinfo="http://www.example.com/enginesinc/customers"> <orderinfo:custId>DWDD39928</orderinfo:custId> <orderinfo:payMethod>PO</orderinfo:payMethod> <orderinfo:refNumber>PPSI998</orderinfo:refNumber> </orderinfo:customer> </env:Header> <env:Body> <order:action type="add" xmlns:order="http://www.example.com/enginesinc/orders"> <order:itemId>XJ443</order:itemId> <order:itemPrice>383902</order:itemPrice> <order:itemQty>3</order:itemQty> </order:action> </env:Body> </env:Envelope>
In this case, a system encountering the message that has been assigned a role of intermediary would process the marketing:activity element because it has a role of http://www.w3.org/2002/12/soap-envelope/role/next, and then remove the marketing:activity element and its contents before passing the message on to its intended receiver. (If desired, it could re-insert the element if it were needed by future intermediaries or the ultimate receiver.) The env:mustUnderstand attribute tells the intermediary that if it can't process this element, it must return a fault, or an error, rather than simply passing the message on. (SOAP also defines a env:relay attribute that, when set to true, tells the system not to remove the element if it hasn't been processed.)
SOAP messages generally come in two different "styles". Some, such as the example here, use the "conversational" style, in which information is simply conveyed, and the application deals with it accordingly. In other cases, you might opt for the "RPC" style, in which case you are requesting a particular action be performed with particular parameters. For example, if this example were in the RPC style, we would be requesting that the action() method be executed with an itemId parameter of XJ443 an itemPrice parameter of 383902, and an itemQty parameter of 3.
Because they are simply XML text, SOAP messages can be sent using virtually any protocol. For example, with the proper headers, the message can be sent within the body of an HTTP POST request, or as the body of anv email.