Comments on: Trends: REST to over take SOAP?

By: Mike T

Mike T — Wed, 04 Nov 2009 18:46:08 +0000

The only SOAP API I have used and come to appreciate is Spring’s API. Spring doesn’t deal with all of that automagic generation bullcrap that most other APIs use. It’s contract first; you define your XML schema in something like XML Spy, build a Spring context that loads some of the Spring objects needed to make sense of it, and then Spring just passes off the income XML to the beans you create and add to the context. It also provides you with about a dozen ways to receive the XML into your beans from JAXB (1.0 and 2.0), JiBX, JDOM, W3C DOM (ie standard Java DOM) and some other means.

By: Stuart

Stuart — Wed, 04 Nov 2009 18:06:28 +0000

I was at the microsoft techdays conference and they had a talk about RESTful services. In the lecture they mentioned that as of right now MS is not making any advances with SOAP, but has added all kinds of support for REST.

One of the points they were driving about SOAP was that because a service specifies the HTTP verb, instead of just using POST like SOAP does, GET requests can be cached.

By: Bryan

Bryan — Wed, 04 Nov 2009 16:58:25 +0000

You are going to find that SOAP is very prevalent because all the Microsoft tools and Java tools make generating SOAP web services trivial. With ASP.NET Web Services, you don’t have to write a WSDL, write the actual soap messages or do anything in XML, its all done in code.

Where SOAP really starts to be painful is when you are writing systems in Python, Ruby, PHP, etc where these automatic and abstractions aren’t as prevalent. REST is easier to program against when you have to actually write the code.

By: uberVU - social comments

uberVU - social comments — Wed, 04 Nov 2009 15:43:17 +0000

Social comments and analytics for this post…

This post was mentioned on Reddit by protium: No.
…