Error Reporting and WSDL-Defined Faults
HydraExpress handles server and client exceptions through rwsf::Exception or one of its derived classes, and SOAP faults through an instance of rwsf::SoapFaultException or one of its generated derivations if a fault is specified in the WSDL file.
A WSDL file can define faults to be caught in the server and returned to the client. One or more faults may be defined for each operation defined in the WSDL. HydraExpress creates a class for each unique fault message type defined. Several faults can use the same message format, so messages are the critical definition needed by HydraExpress to create a mechanism for returning faults to the client.
If faults are defined in the WSDL, the server-side implementation code can detect problems and report them back to the client by throwing one of the defined fault messages.
NOTE: This discussion reflects a traditional request-response operation. For a solicit-response operation, faults would be handled on the client and returned to the server.
For a discussion on exceptions for both the client and server, as well as WSDL-defined faults, see “WSDL-Defined Faults,” in the HydraExpress User Guide.