<?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: A Generic WCF Service for BizTalk</title>
	<atom:link href="http://winterdom.com/2008/05/agenericwcfserviceforbiztalk/feed" rel="self" type="application/rss+xml" />
	<link>http://winterdom.com/2008/05/agenericwcfserviceforbiztalk</link>
	<description>by dæmons be driven</description>
	<lastBuildDate>Thu, 11 Mar 2010 20:28:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Yonathan Masovich</title>
		<link>http://winterdom.com/2008/05/agenericwcfserviceforbiztalk/comment-page-1#comment-1205</link>
		<dc:creator>Yonathan Masovich</dc:creator>
		<pubDate>Thu, 05 Nov 2009 20:48:57 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/05/agenericwcfserviceforbiztalk#comment-1205</guid>
		<description>Hi Tomas,

Thanx for reply.

What you are saying about using orchestration as a responser - it is truly the correct way, but it is still another piece of code to maintain.
The &quot;hack&quot; is just returning &quot;Succeess&quot; or &quot;Failure with description&quot; immidiately after the message was put (or not ☺ )  to the message box.
Anyway, finally we did use one-way WCF with custom binding. 

Though, now there&#039;s another issue with sertificate definitions - it looks like Receive Location&#039;s definition doesn&#039;t keep definition for extension called &quot;context&quot;. After I choose to use Sign only incoming message - and if I export receive location *.config, the line called  stays empty. Even more than that: when I add to *.config desired definition manually -  and import that configuration, and immidiately export configuration back - the definition is cleared.

Here http://social.msdn.microsoft.com/forums/en-US/biztalkr2adapters/thread/46e9345c-cb50-44ce-9084-807b9b3c1c58/   I see the exact problem, with slight difference - that instead of generated client - I have published schemas as WCF - therefore I have no code to add attribute to.

Possibly the solution to my problem will be writing some little WCF-Proxy, which will &quot;pass&quot; to Biztalk non-encrypted message, and the client from other side will contact with that proxy, and not actually Biztalk itself.</description>
		<content:encoded><![CDATA[<p>Hi Tomas,</p>
<p>Thanx for reply.</p>
<p>What you are saying about using orchestration as a responser &#8211; it is truly the correct way, but it is still another piece of code to maintain.<br />
The &#8220;hack&#8221; is just returning &#8220;Succeess&#8221; or &#8220;Failure with description&#8221; immidiately after the message was put (or not ☺ )  to the message box.<br />
Anyway, finally we did use one-way WCF with custom binding. </p>
<p>Though, now there&#8217;s another issue with sertificate definitions &#8211; it looks like Receive Location&#8217;s definition doesn&#8217;t keep definition for extension called &#8220;context&#8221;. After I choose to use Sign only incoming message &#8211; and if I export receive location *.config, the line called  stays empty. Even more than that: when I add to *.config desired definition manually &#8211;  and import that configuration, and immidiately export configuration back &#8211; the definition is cleared.</p>
<p>Here <a href="http://social.msdn.microsoft.com/forums/en-US/biztalkr2adapters/thread/46e9345c-cb50-44ce-9084-807b9b3c1c58/" rel="nofollow">http://social.msdn.microsoft.com/forums/en-US/biztalkr2adapters/thread/46e9345c-cb50-44ce-9084-807b9b3c1c58/</a>   I see the exact problem, with slight difference &#8211; that instead of generated client &#8211; I have published schemas as WCF &#8211; therefore I have no code to add attribute to.</p>
<p>Possibly the solution to my problem will be writing some little WCF-Proxy, which will &#8220;pass&#8221; to Biztalk non-encrypted message, and the client from other side will contact with that proxy, and not actually Biztalk itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2008/05/agenericwcfserviceforbiztalk/comment-page-1#comment-1195</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Mon, 02 Nov 2009 02:30:04 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/05/agenericwcfserviceforbiztalk#comment-1195</guid>
		<description>@Yonathan: I don&#039;t think you&#039;ll be able to do exactly the same. To be honest, the way you&#039;re currently doing it is a bit of a hack. The &quot;right&quot; (if not necessarily the most efficient way to do it) would be to have the called orchestration send a response message right away and then continue on it&#039;s merry way.

I&#039;m curious, though as to what kind of response you could&#039;ve generated on your asmx hack that wasn&#039;t a default &quot;done&quot; response (and if so, why you didn&#039;t just go with a one-way service in the first place)</description>
		<content:encoded><![CDATA[<p>@Yonathan: I don&#8217;t think you&#8217;ll be able to do exactly the same. To be honest, the way you&#8217;re currently doing it is a bit of a hack. The &#8220;right&#8221; (if not necessarily the most efficient way to do it) would be to have the called orchestration send a response message right away and then continue on it&#8217;s merry way.</p>
<p>I&#8217;m curious, though as to what kind of response you could&#8217;ve generated on your asmx hack that wasn&#8217;t a default &#8220;done&#8221; response (and if so, why you didn&#8217;t just go with a one-way service in the first place)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yonathan Masovich</title>
		<link>http://winterdom.com/2008/05/agenericwcfserviceforbiztalk/comment-page-1#comment-1194</link>
		<dc:creator>Yonathan Masovich</dc:creator>
		<pubDate>Sat, 31 Oct 2009 20:30:10 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/05/agenericwcfserviceforbiztalk#comment-1194</guid>
		<description>Hi Tomas,

I&quot;m trying to migrate from some scenario which works for ASMX - to WCF:

Im publishing two schemas, one request and the other - response, as a web service. After I run the wizard, Im changing the generated code in *.cs file of web application - to responde immidiately, and not to wait while some BTS application will respond for the request. Since after running WCF publishiung wizard there&#039;s no any code, just binding and seralization schema, how can I interfere into my request-response flow? Have any idea?</description>
		<content:encoded><![CDATA[<p>Hi Tomas,</p>
<p>I&#8221;m trying to migrate from some scenario which works for ASMX &#8211; to WCF:</p>
<p>Im publishing two schemas, one request and the other &#8211; response, as a web service. After I run the wizard, Im changing the generated code in *.cs file of web application &#8211; to responde immidiately, and not to wait while some BTS application will respond for the request. Since after running WCF publishiung wizard there&#8217;s no any code, just binding and seralization schema, how can I interfere into my request-response flow? Have any idea?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2008/05/agenericwcfserviceforbiztalk/comment-page-1#comment-632</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Tue, 17 Jun 2008 11:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/05/agenericwcfserviceforbiztalk#comment-632</guid>
		<description>@reddy: There&#039;s really no extra code; those two snippets are really all it takes to enable a WCF receive location for BizTalk. Is there anything specifically you&#039;re looking for?
</description>
		<content:encoded><![CDATA[<p>@reddy: There&#8217;s really no extra code; those two snippets are really all it takes to enable a WCF receive location for BizTalk. Is there anything specifically you&#8217;re looking for?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reddy</title>
		<link>http://winterdom.com/2008/05/agenericwcfserviceforbiztalk/comment-page-1#comment-631</link>
		<dc:creator>Reddy</dc:creator>
		<pubDate>Tue, 17 Jun 2008 11:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/05/agenericwcfserviceforbiztalk#comment-631</guid>
		<description>HI ,
Can you please send me the code for above snippet or any webcast related to the above scenario.
Thanks
reddy
</description>
		<content:encoded><![CDATA[<p>HI ,<br />
Can you please send me the code for above snippet or any webcast related to the above scenario.<br />
Thanks<br />
reddy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2008/05/agenericwcfserviceforbiztalk/comment-page-1#comment-630</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Wed, 21 May 2008 15:58:20 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/05/agenericwcfserviceforbiztalk#comment-630</guid>
		<description>Joel: Yes, I&#039;m aware of externalMetadataLocation, but totally forgot about it; thanks for bringing it up.
Actually, I don&#039;t have to worry in this case about the WSDL and the schemas getting out of sync because both are part of a standard control by a third party. So this is really kind of the scenario where this shines!
</description>
		<content:encoded><![CDATA[<p>Joel: Yes, I&#8217;m aware of externalMetadataLocation, but totally forgot about it; thanks for bringing it up.<br />
Actually, I don&#8217;t have to worry in this case about the WSDL and the schemas getting out of sync because both are part of a standard control by a third party. So this is really kind of the scenario where this shines!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel</title>
		<link>http://winterdom.com/2008/05/agenericwcfserviceforbiztalk/comment-page-1#comment-629</link>
		<dc:creator>Joel</dc:creator>
		<pubDate>Wed, 21 May 2008 07:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/05/agenericwcfserviceforbiztalk#comment-629</guid>
		<description>With regards to WSDL, you can expose it by adding and configuring the serviceMetadata section in the BT receive location&#039;s Behavior tab and then setting the externalMetadataLocation property.  The only minor challenge with that is any changes that you make to your messages (i.e. schemas) need to be reflected in the WSDL.  Still, it is a small price to pay for simplicity. :)
We&#039;ve found that replicating a generic service and exposing a WSDL document is so much more efficient and less frustrating than using the BT WCF publishing wizard.
</description>
		<content:encoded><![CDATA[<p>With regards to WSDL, you can expose it by adding and configuring the serviceMetadata section in the BT receive location&#8217;s Behavior tab and then setting the externalMetadataLocation property.  The only minor challenge with that is any changes that you make to your messages (i.e. schemas) need to be reflected in the WSDL.  Still, it is a small price to pay for simplicity. <img src='http://winterdom.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
We&#8217;ve found that replicating a generic service and exposing a WSDL document is so much more efficient and less frustrating than using the BT WCF publishing wizard.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
