http://blogs.msdn.com/richardbpi/archive/2006/11/10/using-only-biztalk-messaging-with-request-response-on-both-ends.aspxSo is BizTalk *really* smart enough to allow me to do request/response operations on both sides of my process without an orchestration in the middle? I set out to prove this scenario out for myself and wanted to share the results. I want to see if I canen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/richardbpi/archive/2006/11/10/using-only-biztalk-messaging-with-request-response-on-both-ends.aspx#1225064Wed, 06 Dec 2006 23:55:51 GMT91d46819-8472-40ad-a661-2c78acb4018c:1225064BizTalkTek<p>Richard:</p> <p>Could this solution be expanded and versatile enough to catch and return a SOAP fault (similar to fault message within an orchestration port</p> <p>1. Business Soap Fault - e.g. Name cannot be more than 5 chars</p> http://blogs.msdn.com/richardbpi/archive/2006/11/10/using-only-biztalk-messaging-with-request-response-on-both-ends.aspx#1226622Thu, 07 Dec 2006 02:17:49 GMT91d46819-8472-40ad-a661-2c78acb4018c:1226622rseroter<p>Hmmm. &nbsp;I can't say for certain what would happen. &nbsp;In our case, the response message is going through a map, so if a SOAP fault did return back down the same pipe, not sure if it would choke on that. &nbsp;</p>