In a messaging-only setup, how can I transform a SOAP fault to a contractual response that the caller expects ?
Remaining Questions:
* Is rewriting AckType message context property enough?
* Why is the exception thrown at the send port being rethrown back to the receive port?
* Why is the NACK treated as a message internal to BizTalk and not available to the ports for transformation?
----------------------------
The following is my messaging setup:
* Two-way receive port with a receive location published in IIS. Receive location is WCF-BasicHttp. Isolated-host, schema only.
* Two-way send port, WCF-SQL.
The caller expects a response of a strong XML type (let's call it a boolean of TRUE or FALSE) depending if the SQL operation is successful, hiding any faults from the caller. I have been struggling with mapping the SOAP fault to the caller's message response contract.
I have created a schema based off the SOAP fault:
<?xml version="1.0" encoding="utf-16"?>
<xs:schema xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" elementFormDefault="qualified" targetNamespace="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import schemaLocation="BTS.xml" namespace="http://www.w3.org/XML/1998/namespace" />
<xs:annotation>
<xs:appinfo>
<b:references>
<b:reference targetNamespace="http://www.w3.org/XML/1998/namespace" />
</b:references>
</xs:appinfo>
</xs:annotation>
<xs:element name="Envelope">
<xs:complexType>
<xs:sequence>
<xs:element ref="s:Body" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Body">
<xs:complexType>
<xs:sequence>
<xs:element ref="s:Fault" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Fault">
<xs:complexType>
<xs:sequence>
<xs:element form="unqualified" name="faultcode" type="xs:NMTOKEN" />
<xs:element form="unqualified" name="faultstring">
<xs:complexType mixed="true">
<xs:attribute ref="xml:lang" use="required" />
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Then created a map from the SOAP fault to the caller's message response. I have tried playing around with maps on both the send and receive ports, as well as different properties within the WCF transports, but the caller always gets back the SOAP fault and not my mapped result:
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body>
<s:Fault>
<faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</faultcode>
<faultstring xml:lang="en-US">The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.</faultstring>
</s:Fault>
</s:Body>
</s:Envelope>
ref: http://bveldhoen.wordpress.com/2010/09/05/messaging-only-request-response-correlation/, http://rohitt-sharma.blogspot.com/2011/03/biztalk-tutorial-part-7-using-two-way.html, http://blogical.se/blogs/johan/archive/2008/03/31/delivery-notifications-outside-orchestrations-a-pure-messaging-approach.aspx
Other recent topics
