Hi,
I had implemented an operation with action "SessionActions.Fault" to catch all the faults coming from Session component. I was not interested in details, but I wanted to ensure any faults coming from session should be handled gracefully. However I noticed that the operation was not invoked when Session raised AddRemoveParticipantsFaultfaults. I had to write a seperate operation to handle AddRemoveParticipantsFaultfaults faults.
Is it correct to say action "SessionActions.Fault" will not catch all faults coming from Session
Thanks,
Ashish Malhotra
Soap faults from Core services
James Alexander
Vasu – I am not sure if you had a chance to look at our documentation online….
If you look at the Session Routing rules specified at the bottom of the page in the following URL, you will get a good understanding on how to handle the routing in general.
http://msdn2.microsoft.com/en-us/library/aa303326.aspx
In any case, try the following, this should work for you.
<Route>
<Criteria> MESSAGE EQ 'Fault' AND MESSAGENS EQ 'http://www.w3.org/2003/05/soap-envelope' OR MESSAGE EQ 'Fault' AND MESSAGENS EQ 'http://schemas.xmlsoap.org/soap/envelope' </Criteria>
<Destination>InitiatorService[ErrorHandleAction]</Destination>
</Route>
Thanks
Jeff54
It appears that an extra forward slash at the end of the namespace does the magic. So please remember to do that when you construct a routing criteria of this sort.
Incorrect format MESSAGE EQ 'Fault' AND MESSAGENS EQ 'http://schemas.xmlsoap.org/soap/envelope'.
Correct format MESSAGE EQ 'Fault' AND MESSAGENS EQ 'http://schemas.xmlsoap.org/soap/envelope/'
Thanks