<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SOAP vs REST &#8212; a common misconception?</title>
	<atom:link href="http://biotext.org.uk/soap-vs-rest-a-common-misconception/feed/" rel="self" type="application/rss+xml" />
	<link>http://biotext.org.uk/soap-vs-rest-a-common-misconception/</link>
	<description>Not a typewriter</description>
	<lastBuildDate>Tue, 07 Sep 2010 11:28:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: anonymous</title>
		<link>http://biotext.org.uk/soap-vs-rest-a-common-misconception/comment-page-1/#comment-47</link>
		<dc:creator>anonymous</dc:creator>
		<pubDate>Mon, 05 Jan 2009 19:39:30 +0000</pubDate>
		<guid isPermaLink="false">http://biotext.org.uk/?p=85#comment-47</guid>
		<description>You can send anything via REST as well. Using the multi-part header, you can upload/download files via rest, you can send documents if you like, whatever you want.

I think SOAP had its place, but REST is a far easier programmatic way to do the same thing. SOAP does have REST on tools support, agreed there, but then, honestly, at least for me and using JSR-311/Jersey, I don&#039;t need tools for REST. You can use a Schema tool for the xml schema, ant/maven will generate the schema-generated java source for the JAXB objects you pass around, the rest is very easy with the exception of sending/receiving files, which is a little more complicated, but only minimal support for files transfers has been implemented at the Jersey API level and it&#039;s not part of the spec either. I am sure this will get more robust as time goes on.</description>
		<content:encoded><![CDATA[<p>You can send anything via REST as well. Using the multi-part header, you can upload/download files via rest, you can send documents if you like, whatever you want.</p>
<p>I think SOAP had its place, but REST is a far easier programmatic way to do the same thing. SOAP does have REST on tools support, agreed there, but then, honestly, at least for me and using JSR-311/Jersey, I don&#8217;t need tools for REST. You can use a Schema tool for the xml schema, ant/maven will generate the schema-generated java source for the JAXB objects you pass around, the rest is very easy with the exception of sending/receiving files, which is a little more complicated, but only minimal support for files transfers has been implemented at the Jersey API level and it&#8217;s not part of the spec either. I am sure this will get more robust as time goes on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://biotext.org.uk/soap-vs-rest-a-common-misconception/comment-page-1/#comment-46</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Mon, 05 Jan 2009 08:25:49 +0000</pubDate>
		<guid isPermaLink="false">http://biotext.org.uk/?p=85#comment-46</guid>
		<description>Point taken, that&#039;s just one of its common use cases. I&#039;ll modify that bit...</description>
		<content:encoded><![CDATA[<p>Point taken, that&#8217;s just one of its common use cases. I&#8217;ll modify that bit&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens</title>
		<link>http://biotext.org.uk/soap-vs-rest-a-common-misconception/comment-page-1/#comment-45</link>
		<dc:creator>Jens</dc:creator>
		<pubDate>Sun, 04 Jan 2009 20:49:01 +0000</pubDate>
		<guid isPermaLink="false">http://biotext.org.uk/?p=85#comment-45</guid>
		<description>REST is for sending XML documents?!?!?

The request is HTTP, the result... whatever you want. JSON, XML, HTML, text...</description>
		<content:encoded><![CDATA[<p>REST is for sending XML documents?!?!?</p>
<p>The request is HTTP, the result&#8230; whatever you want. JSON, XML, HTML, text&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
