When you use the BizTalk WSE Web Services Publishing Wizard, fault message details do not appear as expected (915089)
The information in this article applies to:
- Microsoft BizTalk Adapter for Web Services
SYMPTOMSConsider the following scenario: - In Microsoft BizTalk Server 2004, you add an orchestration that includes a request-response port that has a defined fault message.
- You use the BizTalk WSE Web Services Publishing Wizard to publish the orchestration as a Web service.
In this scenario, fault message details do not appear as expected in the details section of the SoapException exception body. WORKAROUNDTo work around this behavior, manually create an exception in a catch block in the Web service proxy code that is generated by the BizTalk WSE Web Services Publishing Wizard, and then throw the exception to the client computer. The following sample code demonstrates how to do this. try
{
Microsoft.Web.Services2.SoapEnvelope response = this.Invoke(request, "Operation_1", bodyTypeAssemblyQualifiedName, false, false, cookie);
response.Save(@"C:\SoapResponseEnv.xml");
return response;
}
catch(SoapException se)
{
SoapException se1 = new SoapException(se.InnerException.Message.ToString(), SoapException.ClientFaultCode,"http://localhost/FaultMessageProcessing_Proxy/FaultMessageProcessing_FaultMessageOrch_FaultInOut.ashx",se);
throw se1;
} STATUS
This behavior is by design.
Modification Type: | Major | Last Reviewed: | 5/15/2006 |
---|
Keywords: | kbBTSAdapters kbBTS kbtshoot kbprb KB915089 kbAudDeveloper kbAudITPRO |
---|
|