<?xml version="1.0"?>

 
<rss version="2.0">
<channel>
<title>IBM developerWorks : Web services : Articles</title>
<link>http://www.ibm.com/developerworks/</link>
<description>The latest content from IBM developerWorks</description>
<pubDate>07 Dec 2009 13:45:28 +0000</pubDate>
<language>en</language>
<copyright>Copyright 2004 IBM Corporation.</copyright>
<image>
<title>developerWorks</title>
<url>http://www.ibm.com/developerworks/i/dwlogo-small.gif</url>
<link>http://www.ibm.com/developerworks/</link>
</image>

	<item>
		<title><![CDATA[Web services programming tips and tricks: Build a SOAP response envelope with SAAJ and JAX-RPC]]></title> 
		<description><![CDATA[This tip follows up on a previous tip, &quot;Using the &lt;xsd:any/&gt; element for custom serialization,&quot; that described the use of the &lt;xsd:any/&gt; element for custom serialization. While the earlier tip focused on reading and processing a javax.xml.soap.SOAPElement, here the author describes how to create one.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/webservices/library/ws-tip-saaj.html?ca=drs-]]></link> 
		<pubDate>17 Aug 2004 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[Web services Programming Tips and Tricks: WSDL file imports]]></title> 
		<description><![CDATA[This tip explains the nuances of the two types of import statements found in a Web Services Description Language (WSDL) file.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/webservices/library/ws-tip-imports.html?ca=drs-]]></link> 
		<pubDate>09 Jul 2004 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[Web Services programming tips and tricks, Part 4: Bring J2EE and .NET together in a business process using BPEL and WebSphere Business Integration Server Foundation]]></title> 
		<description><![CDATA[Investigate a typical business integration scenario between J2EE (Java(TM) 2 Enterprise Environment) and Microsoft(R) .NET and learn how to build and run a BPEL (Business Process Execution Language) business process on IBM(R) WebSphere(R) Business Integration Server Foundation. In the first three parts of this series about improving interoperability between J2EE technology and .NET, Wangming Ye analyzed the common challenges facing a Web services integration between J2EE and .NET, and offered best practices. This tip focuses on the delicate design of XML schemas that Web services programmers often overlook. The objective is to show how to avert common Web service interoperability challenges between .NET and J2EE, such as nested complex-type arrays, date and time values, and namespace issues, through a top-down approach (WSDL (Web Services Description Language) implementations).]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/webservices/library/ws-tip-j2eenet4/index.html?ca=drs-]]></link> 
		<pubDate>27 May 2005 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[Web services programming tips and tricks: Handle namespaces in SOAP messages you create by hand]]></title> 
		<description><![CDATA[Gain a thorough understanding of how WSDL maps to SOAP. Under normal circumstances, you don&apos;t have to worry about namespaces in the SOAP message.  But there are times when you must. This tip prepares you for those times when you have to create your SOAP message by hand and deal with namespace issues without the help of a tool.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/webservices/library/ws-tip-namespace.html?ca=drs-]]></link> 
		<pubDate>03 May 2005 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[Web services programming tips and tricks: Develop a UDDI Java application for Web services registered within a UDDI registry]]></title> 
		<description><![CDATA[This tip establishes the case for using Universal Description, Discovery, and Integration (UDDI) to register Web services for application-level consumption. It provides detailed code samples and an extension API based on the Universal Description, Discovery, and Integration for Java (UDDI4J) API that will enable you to begin utilizing UDDI for your own development purposes.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/webservices/library/ws-tip-uddijava.html?ca=drs-]]></link> 
		<pubDate>27 Jul 2004 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[Web services tip: Representations of null in XML Schema]]></title> 
		<description><![CDATA[Represent a null value in the XML-equivalent of a field when you map a null Java bean field to XML.  This tip explores and compares a number of ways to do so.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/webservices/library/ws-tip-null.html?ca=drs-]]></link> 
		<pubDate>09 Aug 2005 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[Web services programming tips and tricks: Attachments using the wsi:swaRef XML type from WSI]]></title> 
		<description><![CDATA[This tip describes how to use the XML attachment type defined by wsi:swaRef, the Web services Interoperability organization.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/webservices/library/ws-tip-swaref.html?ca=drs-]]></link> 
		<pubDate>27 Jun 2006 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[Web services hints and tips: JAX-RPC versus JAX-WS, Part 1]]></title> 
		<description><![CDATA[JAX-WS 2.0 is the successor to JAX-RPC 1.1.  This article introduces a series that compares these two Java Web services programming models.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/webservices/library/ws-tip-jaxwsrpc.html?ca=drs-]]></link> 
		<pubDate>06 Oct 2006 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[Web services hints and tips: JAX-RPC versus JAX-WS, Part 2]]></title> 
		<description><![CDATA[JAX-WS 2.0, the successor to JAX-RPC 1.1, has evolved its data mapping methods by using JAXB (the Java Architecture for XML Binding), a JCP-defined technology. This second tip in a series compares the data mappings of these two Web services specifications.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/webservices/library/ws-tip-jaxwsrpc2.html?ca=drs-]]></link> 
		<pubDate>30 Nov 2006 05:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[Web services hints and tips: JAX-RPC versus JAX-WS, Part 3]]></title> 
		<description><![CDATA[This third part of the series about Java(TM) API for XML-based RPC (JAX-RPC) 1.1 and Java API for XML Web Services (JAX-WS) 2.0
      compares the mapping of Web Services Description Language (WSDL) to a service
      endpoint interface (SEI). The concept of an
      SEI was first introduced in JAX-RPC 1.0 and has been maintained in JAX-WS 2.0, with
      some additions. This tip walks you through the major differences.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/webservices/library/ws-tip-jaxwsrpc3/index.html?ca=drs-]]></link> 
		<pubDate>13 Jun 2007 04:00:00 +0000</pubDate>               
	</item>

</channel>
</rss>


