• 1
• 2
• 3
• 4
• 5

abc absolute address addressing ajax api architecture author base based basic body browser call called client code container defined defines description designed details developerworks deviceid document download emerging endpointreference envelope epr extends framework function functionqname getresourceproperty handler header headers http ibm id identifying illustrated implement implementation include information installment invoking java javascript language learn library listing localhost message method methods model number object objects operation operations page part primary rate reference related request resource resourceframework resources review series service services set simple soa soap soapelement soapenvelope specification standards support supporting technical technologies technology top uri var web wrapper ws wsaendpointreference wsahandler wsajs wsamessagecontext wscall wshandler wsjs wsqname wsrf wsrfjs wsrfrequestgetresourceproperty wwwworgaddressing xml xmlns xmlnshttp

Keyword Cloud Navigation Map

Quick Review

In Part 1 of this series, I introduced a cross-browser JavaScript library providing a simple SOAP Web services client capable of RPC encoded and document-literal style requests. Included in that client is support for request and response handlers, custom XML serializers/deserializers, and SOAP Headers; all of which I make use of in this WS-Addressing and WS-ResourceFramework implementation.

The primary objects defined in ws.js (introduced in Part 1) include:

1. WS.Call: A Web Service Client that wraps XMLHttpRequest
2. WS.QName: XML Qualified Name implementation
3. WS.Binder: Base for custom XML serializers/deserializers
4. WS.Handler: Base for Request/Response Handlers
5. SOAP.Element: Base SOAP Element wrapping XML DOM
6. SOAP.Envelope: SOAP Envelope Object extends SOAP.Element
7. SOAP.Header: SOAP Header Object extends SOAP.Element
8. SOAP.Body: SOAP Body Object extends SOAP.Element
9. XML: Cross-platform utility methods for handling XML

Read Full Tutorial...