PUBLIC MARKS with tags rest & clevermarks

So the question remains: has interoperability pretty much been achieved for WS-* through WS-I and the improvements made with the way in which the specifications and standards are developed today, or has the real interoperability challenge moved elsewhere, still to be addressed?

[...] there seems to be no clear answer to whether or not (extended) transactions really do fit in a REST world. However, it does seem conclusive that many people believe they need them for one reason or another.

The Atom Publishing Protocol is an important new standard for content publishing and management. In this article, explore a high-level overview of the protocol and its basic operation and capabilities.

SOAP sur un terrain glissant...

SOA was supposed to reduce costs and increase agility on a massive scale. Except in rare situations, SOA has failed to deliver its promised benefits. After investing millions, IT systems are no better than before.

A key component of a Web service is a formal description with Web Services Description Language (WSDL). Until recently there was no formal language to describe REpresentational State Transfer (REST) Web services—now there's WSDL 2.0.

Why build a RESTful web service for DayTrader? Because I frequently hear that REST can't be applied to complex situations. I also want to use the example as motivation for talking about some of the idioms that are available to handle more extensive requirements.

You may or may not be aware that there is debate going on about the “right” way to implement heterogeneous application-to-application communication: While the current mainstream clearly focuses on web services based on SOAP, WSDL and the WS-* specification universe, a small, but very vocal minority claims there’s a better way: REST, short for REpresentational State Transfer. In this article, I will try to provide a pragmatic introduction to REST and RESTful HTTP application integration without digressing into this debate. I will go into more detail while explaining those aspects that, in my experience, cause the most discussion when someone is exposed to this approach for the first time.

Invariably, learning about REST means that you’ll end up wondering just how applicable the concept really is for your specific scenario. And given that you’re probably used to entirely different architectural approaches, it’s only natural that you start doubting whether REST, or rather RESTful HTTP, really works in practice, or simply breaks down once you go beyond introductory, “Hello, World”-level stuff. In this article, I will try to address 10 of the most common doubts people have about REST when they start exploring it, especially if they have a strong background in the architectural approach behind SOAP/WSDL-based Web services.

There is a giant sucking sound of processing power, time, money, and intellectual resources being used up on this problem, all because someone wants to store a shopping cart in HttpSession.

As REST principals and Web Oriented Architecture concepts are in the process from migrating from the geek edge to the enterprise mainstream, in a recent interview, IBM WebSphere CTO Jerry Cuomo has been saying that they have become a core focus for IBM in Project Zero, which "introduces a simple environment for creating, assembling and running applications based on popular Web technologies."

WSO2 Web Services Framework/PHP (WSO2 WSF/PHP), a binding of WSO2 WSF/C into PHP is a PHP extension based on Apache Axis2/C, Apache Sandesha2/C and Apache Rampart/C for providing and consuming Web Services in PHP. WSO2 WSF/PHP supports both SOAP 1.2 and SOAP 1.1, REST style invocation and WS-* stack specifications: SOAP MTOM, WS-ReliableMessaging, WS-Security 1.0 (2004), WS-Addressing 1.0 and submission. WSO2 WSF/PHP is released under Apache License, Version 2.0

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

Joe Gregorio answered some questions about WADL in his post "Do we need WADL?". Also note that Leonard Richardson has chimed in recently on the WADL issue. And I of course have some different thoughts. :-)

A good way to generate REST WS with ezpublish.

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 paper is about a service bus, a really simple one. What we will describe is a service bus based on RSS, or Really Simple Syndication: a simple protocol for disseminating news on the Internet which has been especially successful in the blogging world. RSS is a basic structure, or protocol for producing information feeds, usually consisting of news headlines. Many people will say that there is nothing enterprise about RSS, and indeed it is often assumed that RSS is too simple to be useful for anything but news.

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.