<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.itworld.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>UDDI</title>
 <link>http://www.itworld.com/uddi</link>
 <description></description>
 <language>xx</language>
<item>
 <title>MuleSource decides to bypass a &#039;check box&#039; feature in its next-gen product</title>
 <link>http://www.itworld.com/development/68726/mulesource-decides-bypass-check-box-feature-its-next-gen-product</link>
 <description>One of the biggest decisions MuleSource CTO Ross Mason faced in 2008 was whether to include UDDI support in the initial releases of its Mule Galaxy SOA registry. Although Mason remained confident that the world was moving away from UDDI, it is often a &quot;check box feature&quot; in the RFPs of organizations looking to adopt an SOA governance tool. So he gambled and instead chose to make a stand that this software category required a new, simpler architecture (namely, REST)
</description>
 <comments>http://www.itworld.com/development/68726/mulesource-decides-bypass-check-box-feature-its-next-gen-product#comments</comments>
 <category domain="http://www.itworld.com/development">Development</category>
 <category domain="http://www.itworld.com/service-oriented-architecture">SOA</category>
 <category domain="http://www.itworld.com/feature">Feature</category>
 <category domain="http://www.itworld.com/mulesource">MuleSource</category>
 <category domain="http://www.itworld.com/rest">REST</category>
 <category domain="http://www.itworld.com/uddi">UDDI</category>
 <pubDate>Tue, 02 Jun 2009 16:38:06 -0400</pubDate>
 <dc:creator>ITworld staff</dc:creator>
 <guid isPermaLink="false">68726 at http://www.itworld.com</guid>
</item>
</channel>
</rss>
