It's tremendously difficult to argue a RESTful approach to a service-oriented architecture (SOA), when the corporate mindshare is SOAP--where project stakeholders tout the SOA buzzword, nod their heads sagely when you say SOAP, nod their heads again when you say XML-RPC, and then look blankly when you mention REST. At an official level, it seems that for the IBMs, Suns, Microsofts, and Oracles (et al) of this world, REST isn't even on the radar; perhaps more because they would find it difficult to build a commercial strategy around something that is based on simplicity and standards (like HTTP) that have been around for years, than from a true lack of visibility at the coalface.
Two reliable delivery specifications create confusion. Examine two Web services specifications that address the problem of reliably delivering messages between Simple Object Access Protocol (SOAP) endpoints: WS-ReliableMessaging (WS-RM) and WS-Reliability (WS-R). Follow along with Doug Davis as he summarizes the key differences and similarities between them.
Press release. "Web services make good on the promise of interoperable applications only when the technical foundations are shared, robust, and achieve expected performance," explained Tim Berners-Lee, W3C Director. "Today, W3C Members have endorsed SOAP Version 1.2, the first version of SOAP to have undergone rigorous testing and implementation, and to support a full complement of Web standards. Web services customers and developers alike demand an XML-based Web services protocol that powers the full range of applications and Web technologies they can imagine using. Now that SOAP Version 1.2 is here, they have it."
Aaron Skonnard of DevelopMentor talks about the difference between document/literal and rpc/encoded Web Services.
SOAP (Simple Object Access Protocol) has become synonymous with XML- based Web services. However, many real-world response-request-type Web services don't use SOAP; instead, they pass XML messages directly over HTTP. This article discusses these two Web service design approaches.
Microsoft's Yasser Shohoud explains why the SOAP messaging format you use for your Web service doesn't necessarily determine the programming model you use. Learn more about SOAP messaging formats and decoupling the message format from the programming model.
W3C Candidate Recommendation 19 December 2002, a non-normative document intended to provide an easily understandable tutorial on the features of the SOAP Version 1.2 specifications. In particular, it describes the features through various usage scenarios, and is intended to complement the normative text contained in Part 1 and Part 2 of the SOAP 1.2 specifications.
This article explains why SOAP encoding, also known as Section 5 encoding, is a shadow from SOAP's past that has no place in the future of Web services.
This article examines ways that SOAP can be used to communicate information in RDF models. It discusses ways of translating the fundamental data in RDF models to the SOAP encoding for PC-like exchange, or for directly passing parts of the model in RDF/XML serialized form.
O'Reilly Network: With the release of Mozilla 1.0, the world now has a browser that supports SOAP natively. No longer do the tasks of assembling, executing, and handling SOAP operations fall solely on the server side. This article shows you how Web applications running...
SoapRPC.com is a resource site for SOAP, .NET, UDDI, Sun ONE, HP Netaction and related protocols for building Web Services.
This is a SOAP client COM component for the Windows family, originally targeted at PocketPC (hence the name), there is also a Win32 version that works on Windows 95/98/Me/NT4/2000/XP. PocketXML-RPC is Open Source.
W3C Note: Simple Object Access Protocol (SOAP) 1.1. Issued on 08 May 2000