<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Custom recoverable interchange processing pipeline components</title>
	<atom:link href="http://biztalkmessages.vansplunteren.net/2009/03/31/custom-recoverable-interchange-processing-pipeline-components/feed/" rel="self" type="application/rss+xml" />
	<link>http://biztalkmessages.vansplunteren.net/2009/03/31/custom-recoverable-interchange-processing-pipeline-components/</link>
	<description>Randal van Splunteren&#039;s experiences with BizTalk Server and other MS technologies.</description>
	<lastBuildDate>Wed, 01 Sep 2010 00:35:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Ratnakar</title>
		<link>http://biztalkmessages.vansplunteren.net/2009/03/31/custom-recoverable-interchange-processing-pipeline-components/#comment-162</link>
		<dc:creator>Ratnakar</dc:creator>
		<pubDate>Tue, 14 Jul 2009 06:42:10 +0000</pubDate>
		<guid isPermaLink="false">http://biztalkmessages.vansplunteren.net/?p=313#comment-162</guid>
		<description>Hi, 

Is the solution applicable to BizTalk 2006? Is Writing property “SuspendMessageOnRoutingFailure” mandatory? We are getting an error when implementing in BTS 2006 :-

pipeline component in the receive pipeline:&quot;FRCRT.DebatchUsingSchema.Demo.DebatchUsingSchema, FRCRT.DebatchUsingSchema.Demo, Version=1.0.0.0, Culture=neutral, PublicKeyToken=afa8b3077939cb6c&quot; is using the message context properties &quot;BTS.MessageDestination&quot; or &quot;BTS.SuspendMessageOnRoutingFailure&quot; in a unsupported fashion. The pipeline processing is being terminated.</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>Is the solution applicable to BizTalk 2006? Is Writing property “SuspendMessageOnRoutingFailure” mandatory? We are getting an error when implementing in BTS 2006 :-</p>
<p>pipeline component in the receive pipeline:&#8221;FRCRT.DebatchUsingSchema.Demo.DebatchUsingSchema, FRCRT.DebatchUsingSchema.Demo, Version=1.0.0.0, Culture=neutral, PublicKeyToken=afa8b3077939cb6c&#8221; is using the message context properties &#8220;BTS.MessageDestination&#8221; or &#8220;BTS.SuspendMessageOnRoutingFailure&#8221; in a unsupported fashion. The pipeline processing is being terminated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: breerfapE</title>
		<link>http://biztalkmessages.vansplunteren.net/2009/03/31/custom-recoverable-interchange-processing-pipeline-components/#comment-96</link>
		<dc:creator>breerfapE</dc:creator>
		<pubDate>Sat, 16 May 2009 13:55:50 +0000</pubDate>
		<guid isPermaLink="false">http://biztalkmessages.vansplunteren.net/?p=313#comment-96</guid>
		<description>Very usefull, Thanks</description>
		<content:encoded><![CDATA[<p>Very usefull, Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leonid Ganeline</title>
		<link>http://biztalkmessages.vansplunteren.net/2009/03/31/custom-recoverable-interchange-processing-pipeline-components/#comment-62</link>
		<dc:creator>Leonid Ganeline</dc:creator>
		<pubDate>Wed, 01 Apr 2009 05:40:48 +0000</pubDate>
		<guid isPermaLink="false">http://biztalkmessages.vansplunteren.net/?p=313#comment-62</guid>
		<description>Nice finding. 
I wonder why the processing of the errors in the messages is not included in the interfaces of the custom pipeline components. The errors can be on each processing stage and we should manage them properly.</description>
		<content:encoded><![CDATA[<p>Nice finding.<br />
I wonder why the processing of the errors in the messages is not included in the interfaces of the custom pipeline components. The errors can be on each processing stage and we should manage them properly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
