I have an Orchestration that both consumes a WCF service and publish one(Two way). In my Orchestration i catch a SOAPException and need to send it as a fault message back to the published WCF service. The problem that i have is that the returned message is full of escape characters (< > " ' &). At first i had the fault message type set to string but then the hole message was full of escapes. then i used a custom schema and inserted the SOAPException.Message in to that structure, but the message part inserted became escaped. What can i do to avoid this?
I need to dig in to the exception message and make decisions whether i should send it as a fault message or send it in a other way depending on the FaultType.
See if the following blog can help you resolve your issue (even though it's written for BizTalk 2006 R2, but I think it's still applicable to BizTalk 2010):
Hope this helps.
"Google skills are more important than your coding skills."
I'm now able to catch the typed exception from the consumed service and forwarding that fault message seams to work. In this case not using the SOAPException was the solution. But still other exceptions that ends up in the SOAPException is still escaped. Maby has some thing to do with this: blogs.msdn.com/.../reading-data-from-xml-strings-in-biztalk-server.aspx
Thanks by the way.