This content has been marked as final. Show 5 replies
I believe you have to add an error handler at the top level replacing the contents of the body variable with $fault... That's usually the way when you have service callouts...
Hope this helps...
have you tried constructing the soap fault yourself in the service error handler and let this come back to the 'calling' service ?
by default it will catch the fault and will construct his own body in the service error handler, so you loose some error details
maybe these help a bit :
thanks for the reply, though this links didn't help me.
I still cant get the original error at the outer flow error handler.
any other ideas?
that's because the service error handler will wrap the fault in his own format1 person found this helpful
so in each service error handler you need to recreate the soap fault with the error stack, and reply that back to the calling service, otherwise you will loose the error details already in the proxy service in which the fault occures.
propagating the error without build the logic in each proxy service won't work if you ask me (and there also isn't a simple checkbox to enable anything on this)
If you can't put Reply action at any stage of error handler then one way is that you can:1 person found this helpful
Manually replace body content with $fault in inner error handler then use resume action at the same place.
This will end up handling fault and sending body(Body which manually contains desired fault structure) as it is in response.