<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://soa.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>SOAP</title>
 <link>http://soa.sys-con.com/</link>
 <description>Latest articles from SOAP</description>
 <language>en</language>
 <copyright>Copyright 2008 </copyright>
 <generator></generator>
 <lastBuildDate>Thu, 04 Dec 2008 22:40:45 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Virtualization - Cisco Reportedly Creates SOAP-Slipping RPC Protocol</title>
 <link>http://soa.sys-con.com/node/579357</link>
 <description>According to CIO.com, Cisco has a new SOAP-replacing messaging protocol called Etch, born out of its Unified Application Environment (UAE), to integrate client/server applications. Cisco reportedly intends to beta the thing this summer as part of UAE 2.5 and ultimately open source it maybe under a Mozilla or Apache license. Apparently it could also replace CORBA and EJB.&lt;p&gt;&lt;a href=&quot;http://soa.sys-con.com/node/579357&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 30 May 2008 12:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://soa.sys-con.com/node/579357</guid>
</item>
<item>
 <title>Does Your SOA Include a Persistence Strategy?</title>
 <link>http://soa.sys-con.com/node/143908</link>
 <description>Truth be told, traditional approaches to integration are really about keeping persistence at the points, within the source or target systems, and replicating data as needed. However with the use of true services, there is a clear advantage in keeping some persistence at a central-tier, for any number of legitimate reasons. Let&#039;s explore this in the context of an SOA.&lt;p&gt;&lt;a href=&quot;http://soa.sys-con.com/node/143908&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 27 Dec 2005 14:00:00 EST</pubDate>
 <guid isPermaLink="true">http://soa.sys-con.com/node/143908</guid>
</item>
<item>
 <title>SOA Web Services: Does Your SOA Achieve Agility?</title>
 <link>http://soa.sys-con.com/node/143900</link>
 <description>Agility seems to be the buzzword du jour. There are &#039;agile enterprises,&#039; &#039;agile manifestos,&#039; &#039;agile programmers,&#039; and &#039;agile architectures.&#039; Slap &#039;agile&#039; in front of just about anything and marketers believe it will sell better. Yet, one of the primary goals of using service-based architectures was to create &#039;agile systems.&#039;  This begs the question, was it just marketing or is there something to it?&lt;p&gt;&lt;a href=&quot;http://soa.sys-con.com/node/143900&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 10 Nov 2005 09:00:00 EST</pubDate>
 <guid isPermaLink="true">http://soa.sys-con.com/node/143900</guid>
</item>
<item>
 <title>How H&amp;R Block Has Maximized Its Return on SOA Web Services</title>
 <link>http://soa.sys-con.com/node/143899</link>
 <description>Working with service-oriented applications is a lot like doing your taxes because: there&#039;s really no avoiding it, you need to keep track of a number of different factors, you must maintain a record of data to protect against audits and plan for the future, and you&#039;d better catch any mistakes or you&#039;ll have a problem on your hands faster than you can spell &#039;SOA.&#039;&lt;p&gt;&lt;a href=&quot;http://soa.sys-con.com/node/143899&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 07 Nov 2005 19:45:00 EST</pubDate>
 <guid isPermaLink="true">http://soa.sys-con.com/node/143899</guid>
</item>
<item>
 <title>Mindreef Ushers In Online Web Services Diagnostics (Live on SYS-CON.TV)</title>
 <link>http://soa.sys-con.com/node/48421</link>
 <description>Mindreef is making it easier for Web services problems to be resolved, Mark Ericson - CTO of Mindreef - told SYS-CON.TV (&lt;a href=&quot;http://sys-con.tv&quot; title=&quot;http://sys-con.tv&quot;&gt;http://sys-con.tv&lt;/a&gt;) at Web Services Edge 2005 recently in Boston. v4.1 of SOAPscope Web services diagnostic tool allows over-the-Web collaboration between developers.&lt;p&gt;&lt;a href=&quot;http://soa.sys-con.com/node/48421&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 03 Mar 2005 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://soa.sys-con.com/node/48421</guid>
</item>
<item>
 <title>IBM&#039;s Next DB2 Content Manager Will Simplify Programming</title>
 <link>http://soa.sys-con.com/node/45756</link>
 <description>IBM&#039;s &#039;Project Cinnamon,&#039; still in beta but due to be released with IBM&#039;s next DB2 release, will put XML at the heart of DB2 Content Manager and allow customers to create automatically the data model of a database based on the document type definitions or XML schemas they choose.&lt;p&gt;&lt;a href=&quot;http://soa.sys-con.com/node/45756&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 30 Jul 2004 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://soa.sys-con.com/node/45756</guid>
</item>
<item>
 <title>Advanced Web Services Policies &amp; Microsoft WSE</title>
 <link>http://soa.sys-con.com/node/45103</link>
 <description>While widely adopted or standardized security protocols are great for interoperability, a set of SOAP message header elements as well as a few new elements that belong in the message body are outside the scope of the existing mechanism for publishing service descriptions, which is WSDL.&lt;p&gt;&lt;a href=&quot;http://soa.sys-con.com/node/45103&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 04 Jun 2004 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://soa.sys-con.com/node/45103</guid>
</item>
<item>
 <title>Advanced Data Management with Web Services Using SOAP&amp; XML Query</title>
 <link>http://soa.sys-con.com/node/39342</link>
 <description>The momentum behind Web services is building. If you haven&#039;t heard about them by now, you&#039;ve probably been living in a jungle or some remote area for the last few years. The underlying technologies of Web services are XML, HTTP, SOAP, WSDL, and UDDI. XML provides an open standard for data exchange, HTTP an open transport protocol, SOAP a remote method invocation protocol, WSDL the service description language, and UDDI a service discovery and registry.&lt;p&gt;&lt;a href=&quot;http://soa.sys-con.com/node/39342&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 11 Jan 2002 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://soa.sys-con.com/node/39342</guid>
</item>
<item>
 <title>Sending Out-of-Band Messages to SOAP-Based Web Services</title>
 <link>http://soa.sys-con.com/node/39285</link>
 <description>SOAP, the Simple Object Access Protocol, is a lightweight toolkit for building Web services. It is an amalgam of ubiquitous technologies - HTTP and XML. Though the likes of Microsoft, IBM, and the Apache Software Foundation normally have little in common, all support it as a foundation for deploying Web services. One of the great advantages of SOAP&#039;s lightweight nature is the simplicity of server-side programming. A SOAP service needs no knowledge of the SOAP environment. In fact, just about any Java class that exposes public methods can be turned into a SOAP service.&lt;p&gt;&lt;a href=&quot;http://soa.sys-con.com/node/39285&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 21 Oct 2001 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://soa.sys-con.com/node/39285</guid>
</item>
</channel>
</rss>
