<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Re: SOA-Q: WSDL rules or sucks?</title>
	<link>http://blog.springsource.com/arjen/archives/2006/03/31/re-soa-q-wsdl-rules-or-sucks/</link>
	<description>A blog about programming in .NET and Java</description>
	<pubDate>Thu, 20 Nov 2008 12:28:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: marten.gustafson &#187; WSDL</title>
		<link>http://blog.springsource.com/arjen/archives/2006/03/31/re-soa-q-wsdl-rules-or-sucks/#comment-343</link>
		<pubDate>Sun, 02 Apr 2006 07:58:38 +0000</pubDate>
		<guid>http://blog.springsource.com/arjen/archives/2006/03/31/re-soa-q-wsdl-rules-or-sucks/#comment-343</guid>
					<description>[...] Arjen Potsuma writes in his reply to Jimmy &amp;#8230;a WSDL may not be the best way to describe a Web service contract, but it’s the best we have right now&amp;#8230; For me, working at a company with a complete concept and, sort of, process for EAI projects, WDSL not that&amp;#8217;s interesting from a contract point of view either since we have formal contracts. Our concept of a contract is also much broader than a simple WSDL, we govern things such as availability, security, performance etc. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Arjen Potsuma writes in his reply to Jimmy &#8230;a WSDL may not be the best way to describe a Web service contract, but it’s the best we have right now&#8230; For me, working at a company with a complete concept and, sort of, process for EAI projects, WDSL not that&#8217;s interesting from a contract point of view either since we have formal contracts. Our concept of a contract is also much broader than a simple WSDL, we govern things such as availability, security, performance etc. [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
