SOAP
Tags:
Digital Identity
:: ebMS
:: IT Governance
:: REST
:: Service-Oriented Architecture
:: Web Services
:: WS-specs
:: XML
:: XML-RPC
Links
Sun technologist: SOAP stack a 'failure'http://www.infoworld.com/article/08/07/24/Sun-technologist-SOAP-stack-a-failure_1.html InfoWorld, Paul Krill, July 24, 2008: The SOAP stack for Web services was branded a failure this week by Tim Bray, a Sun Microsystems technologist and co-inventor of XML, who hailed the REST (Representational State Transfer) mechanism as a SOAP alternative. "The SOAP stack is generally regarded as an embarrassing failure these days," said Bray, who is Sun director of Web technologies, in an interview Wednesday afternoon at the O'Reilly Open Source Convention (OSCON) in Portland, Ore. "REST does what [the SOAP stack] was trying to do in a much more viable, elegant, cheap, affordable way except that we've got no tooling around it yet."- Web Services - SOAP - |
7 votes
|
Interoperability at the SOAP message levelhttp://www-128.ibm.com/developerworks/webservices/library/ws-soa-intersoap/index.html Can a commonly agreed-upon XML schema guarantee a successful data exchange between systems using Web services? Find the answer in this case study. You'll see how to define a WSDL document to achieve interoperability at the SOAP message level when an integration layer is involved. Both Remote Procedure Calls (RPC) and document styles of Web service are discussed.- SOAP - Interoperability - |
1 vote
|
XFire- Open source, high performance SOAPhttp://docs.codehaus.org/display/XFIRE/Home The Codehaus XFire team is proud to announce their 1.0 release! XFire is an open source Java SOAP framework built on a high performance, streaming XML model. XFire includes support for web service standards, an easy to use API, Spring integration, JBI support, and plugable bindings for POJOs, JAXB, and XMLBeans. XFire 1.0 includes support for WSDL 1.1, SOAP 1.1 and 1.2, WS-Addressing, WS-I Basic Profile 1; Pluggable bindings for POJOs, XMLBeans, JAXB 1.1, JAXB 2.0, and Castor support; Support for many different transports - HTTP, JMS, XMPP, In-JVM, etc.; Spring, Pico, Plexus, Loom, and Yan support; JBI Support; Embeddable and Intuitive API; Client and server stub generation; and JSR 181 2.0 API to configure services via Java 5 and 1.4 (Commons attributes JSR 181 syntax).- Web Services - SOAP - |
1 vote
|
Playing Together Nicely: Getting REST and SOAP to Share Each Other's Toyshttp://www.onjava.com/pub/a/onjava/2006/02/15/jython-soap-interface-to-rest.html 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.- Web Services - REST - SOAP - |
|
WS-RM and WS-R: Can SOAP be reliably delivered from confusion?http://www-106.ibm.com/developerworks/library/ws-rmpaper/ 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.- WS-specs - SOAP - |
|
SOAP Version 1.2 Published as a W3C Recommendation.http://xml.coverpages.org/ni2003-06-24-a.html From Cover Pages. With relevant links and more.- SOAP - |
|
World Wide Web Consortium Issues SOAP Version 1.2 as a W3C Recommendationhttp://www.w3.org/2003/06/soap12-pressrelease.html.en 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."- SOAP - |
|
Web Services Encoding and Morehttp://msdn.microsoft.com/msdnmag/issues/03/05/XMLFiles/default.aspx Aaron Skonnard of DevelopMentor talks about the difference between document/literal and rpc/encoded Web Services.- SOAP - |
|
Why Use SOAP?http://www.artima.com/webservices/articles/whysoap.html 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.- SOAP - |
|
RPC/Literal and Freedom of Choicehttp://msdn.microsoft.com/webservices/default.aspx?pull=/library/en-us/dnwebsrv/html/rpc_literal.asp 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.- SOAP - |
|
phpPatterns - Extending PEAR::SOAP WSDLhttp://www.phppatterns.com/index.php/article/articleview/40/1/2/ Using the PEAR::SOAP SOAP_WSDL to generate client proxy code for other PHP SOAP implementations (this could be extended to other languages...)- SOAP - |
|
phpPatterns - PEAR::SOAP Client Fast Starthttp://www.phppatterns.com/index.php/article/articleview/39/1/2/ A quick example of how easy it is to consume web services with PHP, using PEAR::SOAP and WSDL, as there isn't much material around.- SOAP - |
|
phpPatterns - PEAR::SOAP Server Quick Starthttp://www.phppatterns.com/index.php/article/articleview/41/1/2/ How to create SOAP servers with PEAR::SOAP.- SOAP - |
|
SOAP testing easier said than donehttp://www.adtmag.com/article.asp?id=7455 Testing tools and methodologies for the web are in their infancy, most observers agree. The good news, though, is that some concepts and tools to help get you started do exist, and more are coming in the next few years.- SOAP - |
|
Generating PHP SOAP Servers from WSDL with XSLThttp://www.phppatterns.com/index.php/article/articleview/24/1/2/ WSDL is an XML format for describing web services. Constructing PHP clients from WSDL is no problem but as WSDL is uses XML schema (which is effectively strongly typed), the relationship between PHP and WSDL on the server side is not so fine. Rather than generating WSDL from a PHP server, this is an experiment in generating PHP from WSDL, with help from a little XSLT.- SOAP - |
|
SOAP Serviceshttp://www.topxml.com/soap/articles/soapservices/default.asp By Chris Dix from the book "Professional XML Web Services"- SOAP - |
|
From XML-RPC to SOAP: A Migration Guidehttp://www.xml.com/pub/a/2002/12/18/endpoints.html In his XML.com Endpoints column, Rich Salz offers guidance for migrating from XML-RPC to SOAP by creating a SOAP profile with which XML-RPC can interoperate.- SOAP - |
|
SOAP Version 1.2 Part 0: Primerhttp://www.w3.org/TR/soap12-part0/ 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.- SOAP - |
|
The Argument Against SOAP Encodinghttp://msdn.microsoft.com/webservices/default.aspx?pull=/library/en-us/dnsoap/html/argsoape.asp 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.- Web Services - SOAP - |
|
Using RDF with SOAPhttp://www-106.ibm.com/developerworks/webservices/library/ws-soaprdf/ 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.- RDF - SOAP - |
1 vote
|
Using the Mozilla SOAP APIhttp://www.oreillynet.com/pub/a/javascript/synd/2002/08/30/mozillasoapapi.html 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...- SOAP - |
|
Slippery SOAP: The 2-Sides of SOAPhttp://www.prescod.net/soap/views/ A scratch-pad where Paul Prescod documents the world's different views of SOAP.- SOAP - |
|
SoapRPC.com: Webservice ResourcesSoapRPC.com is a resource site for SOAP, .NET, UDDI, Sun ONE, HP Netaction and related protocols for building Web Services.- SOAP - |
|
XML-RPC vs. SOAPhttp://weblog.masukomi.org/writings/xml-rpc_vs_soap.htm Kate Rhodes: A simple guide to choosing the best protocol for your XML Remote Procedure Call needs.- XML-RPC - SOAP - |
|
