What should be the convention for returning errors to the remote client?
Should we throw Exceptions or SoapFaults?
I've been working on trying to standardize error handling from our code.
For some of our capability operations, we can explicitly throw a
SoapFault. This is good because we can set a specific error code and
message, and a client can catch the faults and respond according to the
error code.
But in many other areas, both outside of our capability code and within,
general Exceptions are thrown instead. So we cannot control how the
errors are sent to the client. I'd like to know how to make the error
handling better so that a client can get errors in a consistent manner
and respond in an automated fashion.
