PUBLIC MARKS from nhoizey with tag soap

SOAP sur un terrain glissant...

Amazon has both SOAP and REST interfaces to their web services, and 85% of their usage is of the REST interface. Despite all of the corporate hype over the SOAP stack, this is pretty compelling evidence that developers like the simpler REST approach.

I think we had one person inquire about using the SOAP version of the API. I don't know if any apps were actually built. There is at least one application built on XML-RPC. But all the others--I don't even know how many there are--are built on the REST AP

WSO2 WSF/PHP is a complete solution for building and deploying Web services, and is the only PHP extension with the widest range of WS-* specification implementations

Once again the participants in the SOA discussion group have got themselves all riled up about what exactly SOA is and why it may or may not be working.

REST is for data-oriented applications that focus on create/read/update/delete scenarios. Solution based on WS-* for service/method-oriented applications, especially those that need more advanced behaviors such as transactions and more-than-basic security

Ce mois-ci, je vais vous présenter l'univers passionnant de BizTalk Server 2006 et sa prise en charge pour les technologies de services Web d'aujourd'hui. Vous apprendrez à utiliser les adaptateurs SOAP et WSE (Web Services Enhancements) déjà disponibles et je vous parlerai du nouvel adaptateur Windows® Communication Foundation (WCF) inclus dans BizTalk® Server 2006 R2.

"The place to really watch, if you're a conservative watcher and you don't want to watch much in the industry about these emerging specifications is WS-I," he said. "It's putting together answers to technical questions that people need answered if they want things to work together for Web services interoperability."

Almost everyone has at least heard of SOAP. Few people have heard of REST. But both are jockeying for the mindshare of developers trying solve problems building applications on the web. REST by virtue of existing, and SOAP largely by virtue of backing by software vendors and standards bodies.

This article shows Interoperability based on OASIS WS-Security 1.0 between Microsoft WSE 2.0 and Systinet Server for Java 5.0. The walkthroughs in this article will take you through all you need to know to configure the two environments for securely signing and encrypting SOAP requests and responses using X509 certificates.

A WS-Transfer interaction is based on the REST architectural style (it looks like its SOAP implementation) where four interfaces can handle the creation and operation of the resource state. There is a CRUD (Create/Retrieve/Update/Delete) style in the resource state, the same way it is in the database layer - database record.

Is HTTP GET/POST enough for you? Fine. Then you are simply not the 'right target' for web services evangelists ;-)

Will there be still 97% of simple REST services on the web then? Yes, sure. WS-* does not compete with browser-oriented applications or simple-get-then-do-regexp interactions

acceptable levels of tolerance differ depending on whether or not a given operation is safe or not

A hallmark of fundamentalism is a desire to apply simple rules ("programs are declarative," "there is no operation but POST", "services are stateless") to all situations. But computing is a large and varied world, with few opportunities for absolutist statements.

to implement Web Services Security with the X.509 Certificate Profile, you also need to implement XML Signature (which includes XML Canonicalization and XML Exclusive Canonicalization) and XML Encryption. To correctly handle imports of WSDL1.1 documents (and validate the traffic they describe), you need to support the entire behemoth that is XML Schema -- in particular if you are attempting to support RPC-oriented SOAP, which informally requires you to support the entire XML Schema Datatypes specification. Don't forget support for SOAP with Attachments, either!

A generic client written in PHP and capable of secure and non-secure calls for use in testing Web services.

It doesn't matter if a partner uses REST or SOAP, he pointed out. "Our developers don't care if it's REST or SOAP. It's all about customers," he said.

Enterprise integration is a complex field, and there is no simple 'cookbook' answer. Patterns are accepted solutions to recurring problems within a given context. They are abstract enough to apply to most integration technologies, but specific enough to provide hands-on guidance to designers and architects. Patterns also provide a vocabulary for developers to efficiently describe their solution.

Apache ServiceMix is an Enterprise Service Bus (ESB) that combines the functionality of a Service Oriented Architecture (SOA) and an Event Driven Arthitecture (EDA) to create an agile, enterprise ESB.

There's a lot we can learn from CORBA's mistakes

This tool is designed for testing existing Web services from a LAMP environment. When given a Web Service Definition Language (WSDL) specification, this tool is capable of secure and non-secure calls