Currently, it is impossible to throw either WebServiceExceptions or customs excpetions from WSDL which have a different faultcode than S:Server. This is really annoying because you neither can provide custom faultcodes nor can you even use standard ones like S:Client to signal a client error, e.g., invalid input. This all leads to bad interface design. The only way is to use SOAPFault with SOAPFaultException but this is real pain.
Currently, it is impossible to throw either WebServiceExceptions or customs excpetions from WSDL which have a different faultcode than S:Server. This is really annoying because you neither can provide custom faultcodes nor can you even use standard ones like S:Client to signal a client error, e.g., invalid input. This all leads to bad interface design. The only way is to use SOAPFault with SOAPFaultException but this is real pain.
Affected Versions
[2.2.8]