Sanjiva Weerawarana writes:
So why do we have all this debate? Its because WS-* implementors (including myself until we did WSO2 Tungsten and Apache Axis2), took the view that REST is not important and ignored it. Duh. We were wrong. Sorry. A thousand apologies. So now, we have a solution: both can be done using one middleware, one programming model and one set of tools.
Which I believe is wrong. Paraphrasing my own comment from the service-orientated architecture mailing list: Similarly to SCA, this approach seem to ignore that there is a larger difference between REST and SOAP than it might seem to a WS proponent at first sight. In REST, you have lots and lots of resources all supporting the same interface; in SOA(P) (at least the wide-spread paradigm), you have few endpoints all supporting different interfaces. In other words, the different is much bigger than just adding a (virtual) SOAP envelope and turning a GET request into XML.
Eloquently put. The “nature” of the service(s) should drive the “architectural” style used. Mixing them both up in the same middleware makes it all the more confusing and complex.