This content has been marked as final. Show 2 replies
Unfortunately it is a bug. It's being tracked and we'll have it fixed in an upcoming release. In the mean time you should be able to get OSB to route on the content of the message rather than the HTTP status code1 person found this helpful
Yes dealing with it is no big deal, just means I have to "sniff" the content and raise an error if it is a SOAP fault to properly propagate the error to the caller.