<?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: Talking to a Tomcat-Hosted Web Service from .NET</title>
	<atom:link href="http://bobondevelopment.com/2007/11/05/talking-to-a-tomcat-hosted-web-service-from-net/feed/" rel="self" type="application/rss+xml" />
	<link>http://bobondevelopment.com/2007/11/05/talking-to-a-tomcat-hosted-web-service-from-net/</link>
	<description>Musings on the craft and business of software development</description>
	<lastBuildDate>Thu, 26 Aug 2010 03:21:57 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris R. Chapman</title>
		<link>http://bobondevelopment.com/2007/11/05/talking-to-a-tomcat-hosted-web-service-from-net/comment-page-1/#comment-3069</link>
		<dc:creator>Chris R. Chapman</dc:creator>
		<pubDate>Wed, 07 Nov 2007 02:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://bobondevelopment.com/2007/11/05/talking-to-a-tomcat-hosted-web-service-from-net/#comment-3069</guid>
		<description>Excellent post - I love this kind of investigative research that pulls in something from an apparently unrelated angle that turns up a valuable clue.

I think you&#039;re on the right track - I worked on a project a couple of years ago with similar circumstances.  In our case, the breakdown was because the Java team were *hand coding* their SOAP packets, and introduced bogus characters that caused the service proxies to barf on the .NET side.

We used SOAPScope a lot to ferret the issue out and pinpoint it.  The Java guys were in denial until we showed them that it was their fault... ;-)</description>
		<content:encoded><![CDATA[<p>Excellent post &#8211; I love this kind of investigative research that pulls in something from an apparently unrelated angle that turns up a valuable clue.</p>
<p>I think you&#8217;re on the right track &#8211; I worked on a project a couple of years ago with similar circumstances.  In our case, the breakdown was because the Java team were *hand coding* their SOAP packets, and introduced bogus characters that caused the service proxies to barf on the .NET side.</p>
<p>We used SOAPScope a lot to ferret the issue out and pinpoint it.  The Java guys were in denial until we showed them that it was their fault&#8230; ;-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
