<?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: WSDL Anti-Pattern: The &#8216;Single XML String&#8217; Service</title>
	<atom:link href="http://blog.danzrobok.com/2008/04/23/wsdl-anti-pattern-the-single-xml-string-service/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.danzrobok.com/2008/04/23/wsdl-anti-pattern-the-single-xml-string-service/</link>
	<description>Business Integration and SOA with an IBM WebSphere slant</description>
	<lastBuildDate>Tue, 17 Aug 2010 21:36:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dan</title>
		<link>http://blog.danzrobok.com/2008/04/23/wsdl-anti-pattern-the-single-xml-string-service/comment-page-1/#comment-118</link>
		<dc:creator>dan</dc:creator>
		<pubDate>Wed, 23 Apr 2008 15:52:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danzrobok.com/2008/04/23/wsdl-anti-pattern-the-single-xml-string-service/#comment-118</guid>
		<description>Hi Arnold, 

I think it comes from a fear that because the WSDL is shared with service consumers, there is too much overhead in having to line everyone up to change. 

What most people don&#039;t realize is that the WSDL a client uses and the WSDL that the provider use could be out-of-sync and everything will still work. If the client doesn&#039;t want to update, the service provider can just ensure that the &#039;old&#039; XML is valid while creating a new WSDL. (ie optional fields etc)

Minimizing change is a great concept, it just gets applied a the wrong level.</description>
		<content:encoded><![CDATA[<p>Hi Arnold, </p>
<p>I think it comes from a fear that because the WSDL is shared with service consumers, there is too much overhead in having to line everyone up to change. </p>
<p>What most people don&#8217;t realize is that the WSDL a client uses and the WSDL that the provider use could be out-of-sync and everything will still work. If the client doesn&#8217;t want to update, the service provider can just ensure that the &#8216;old&#8217; XML is valid while creating a new WSDL. (ie optional fields etc)</p>
<p>Minimizing change is a great concept, it just gets applied a the wrong level.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arnold</title>
		<link>http://blog.danzrobok.com/2008/04/23/wsdl-anti-pattern-the-single-xml-string-service/comment-page-1/#comment-117</link>
		<dc:creator>Arnold</dc:creator>
		<pubDate>Wed, 23 Apr 2008 15:47:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danzrobok.com/2008/04/23/wsdl-anti-pattern-the-single-xml-string-service/#comment-117</guid>
		<description>Hallelujah - oh how I&#039;ve seen that anti-pattern has come around to bite corporations in the arse time and time again... here&#039;s the next question I keep getting - why should we be worried about strict typing and validation anyways :)</description>
		<content:encoded><![CDATA[<p>Hallelujah &#8211; oh how I&#8217;ve seen that anti-pattern has come around to bite corporations in the arse time and time again&#8230; here&#8217;s the next question I keep getting &#8211; why should we be worried about strict typing and validation anyways <img src='http://blog.danzrobok.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
