- 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
We first meet the Web Services Resource Framework in the context of Grid Computing. Grid Computing, designed as it is to spread the work of computation over multiple geographically separated computers, seems a perfect application for web services, but herein we find a problem.
By nature, web services are stateless. Like a HTTP request, once the request is made and the response returned, there is no connection between the requestor and the requestee. If you want to create a "conversational" type service, in which one request/response builds on the previous request/response, you have to build it into your application, adding information such as session ids or other information.
Grid Computing, and thus Web Services Resource Framework, requires a slightly different look at the issue of state.
The white paper Modeling Stateful Resources with Web Services, which explains much of the philosophy involved, describes "A service that acts upon stateful resources" as one that "provides access to, or manipulates a set of logical stateful resources (documents) based on messages it sends and receives". In this case, we're talking about a service in which the "state" that comes into play is the state of the resource itself, as opposed to the state of the conversation.
Being able to find these "resources" is vital in a distributed environment such as Grid Computing, where the same resource might be acted on by multiple clients on multiple computers. To do that, we need two pieces of information. First, we need to identify the web service to call as an endpoint, typically as a URL. Second, we need some kind of identifier for the "stateful resource" itself. Fortunately, we can get that.
Consider this WS-Addressing message:
<wsa:EndpointReference> <wsa:Address> http://www.example.com/services/someService </wsa:Address> <wsa:ReferenceProperties> <tns:resourceID>DataChunk42</tns:resourceID> </wsa:ReferenceProperties> </wsa:EndpointReference>
The resourceID
identifies the actual resource to be
acted on by the web service. The web service gets that information
because the WS-Addressing specification states that it goes into the
header of the SOAP message, as in:
<SOAP-ENV:Envelope> <SOAP-ENV:Header> <tns:resourceID>DataChunk42</tns:resourceID> </SOAP-ENV:Header> <SOAP-ENV:Body> ... </SOAP-ENV:Body> </SOAP-ENV:Envelope>
Note that the web service "requestor" is specifically forbidden from
trying to interpret the resourceID
-- you must leave that for
the web service itself -- but that it's permissible
to create a web service request that retrieves information about the
resource. For example, if you wanted to find out the current processed
value of DataChunk42
and how many iterations it's been through,
you could use the WS-Resource Property namespace and its GetMultipleResourceProperties
request:
<SOAP-ENV:Envelope> <SOAP-ENV:Header> <tns:resourceID>DataChunk42</tns:resourceID> </SOAP-ENV:Header> <SOAP-ENV:Body> <wsrp:GetMultipleResourceProperty> <wsrp:ResourceProperty>currentValue</wsrp:ResourceProperty> <wsrp:ResourceProperty>numIterations</wsrp:ResourceProperty> </wsrp:GetMultipleResourceProperty> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
(You can use GetMultipleResourceProperty
for one or more properties.)
OK, so how do you know those properties are available? The answer is that those properties are defined according to the WS-Resource Properties specification, and then associated with the web service itself. For example, we can use XML Schema to define our properties:
<xs:element name="DataChunkProperties"> <xs:complexType> <xs:sequence> <xs:element name="currentValue" type="string" /> <xs:element name="numIterations" type="int" /> </xs:sequence> </xs:complexType> </xs:element>
We can then associate it with the web service by including this definition in the WSDL file and
then referencing it in the portType
:
<wsdl:definitions targetNamespace="http://example.com/services/resources/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:wsrp="http://www.ibm.com/xmlns/stdwip/web-services/ws-resourceProperties" xmlns:tns="http://example.com/services/resources/"> <wsdl:types> <xs:schema> <xs:import namespace="http://example.com/services/resources/" schemaLocation="http://example.com/services/resources/definitions.xsd"/> </xs:schema> </wsdl:types> … <wsdl:portType name="ChunkProcessor" wsrp:ResourceProperties="tns:DataChunkProperties"> ... </wsdl:portType> … </wsdl:definitions>
So that's the basics of what a resource is, and how it's integrated with a web service. The actual Web Services Resource Framework is a collection of several specifications. I'll be covering them individually in later guide entries when they're a little more fully cooked, but for now, check out the resources for direct links to them in their current states.