|
Home > Archive > BizTalk Server > July 2004 > How to handle soap faults from web services
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
How to handle soap faults from web services
|
|
|
| Hi,
I have a web service that I call, the response from the web service could be a soap fault. The port that calls the webservice doesn't have the ability to add a fault message, if this is the case how do I add this so that I can handle errors from the webs
ervice?
--
John
| |
| Allen Zhang 2004-07-09, 3:32 pm |
| You can capture the System.Web.Services.Protocol.SoapException inside of
the orchestration around the send shape in an atomic scope.
Steps:
1. Create a Scope shape, put the send shape inside.
2. Right click Scope shape and New Exception Handler.
3 In the exception handler select the type of the exception
4. In the exception handler, create an expression shape, inside you can
assign the exception for later decision branching
You will also need to set DeliveryNotification to Transmitted on the send
port.
Thanks
- Allen Zhang (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>
> Hi,
>
> I have a web service that I call, the response from the web service could
be a soap fault. The port that calls the webservice doesn't have the
ability to add a fault message, if this is the case how do I add this so
that I can handle errors from the webservice?
>
> --
> John
>
| |
| Christof [MVP] 2004-07-09, 3:32 pm |
| Allen, please can you clarify this. I'm a little confused.
If you use an atomic scope, your message will not be commited to the message
box until it has finished. So, how would this work? Did you actually try
this please? (I'm actually not sure you can use the deliveryNotification in
this scenario.)
Best regards!
Christof
--
Christof [Microsoft BizTalk Server MVP]
"Allen Zhang (MSFT)" <azhang@online.microsoft.com> wrote in message
news:AjxDnQHZEHA.3168@cpmsftngxa06.phx.gbl...
> You can capture the System.Web.Services.Protocol.SoapException inside of
> the orchestration around the send shape in an atomic scope.
>
> Steps:
> 1. Create a Scope shape, put the send shape inside.
> 2. Right click Scope shape and New Exception Handler.
> 3 In the exception handler select the type of the exception
> 4. In the exception handler, create an expression shape, inside you can
> assign the exception for later decision branching
>
> You will also need to set DeliveryNotification to Transmitted on the send
> port.
>
> Thanks
>
> - Allen Zhang (MSFT)
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> --------------------
could[vbcol=seagreen]
> be a soap fault. The port that calls the webservice doesn't have the
> ability to add a fault message, if this is the case how do I add this so
> that I can handle errors from the webservice?
>
|
|
|
|
|