A fault message should be generated whenever a failure occurs at an intermediary.
每当中介体发生故障时，都应该生成错误消息。
Any response or fault message is mapped out to the status field in the return message.
任何响应或错误消息将被映射到返回消息中的状态字段。
If you disassociate the fault message name from the operation name, you can reuse that message without it looking strange (see Listing 3).
如果将错误的消息名称与操作名称分离，则可以重用该消息，并且看起来也不感到陌生(请参见清单3)。
The service implementation USES the SOAPFaultException to explicitly raise faults so that the exact SOAP 1.1 fault message contents can be determined.
该服务实现使用SOAPFaultException来显式引发错误，以便能够确定精确的SOAP 1.1错误消息内容。
You can define another fault message that reuses your existing fault element, but JAX-RPC maps it to yet another exception; it doesn't reuse the existing exception.
您可以定义重用现有错误元素的另一个错误消息，但是JAX - RPC仍将其映射为另一个异常；它不重用现有异常。
However, in certain circumstances, for example, when either a back-end system or a database that a service requires is not available, the service might respond with a fault message.
但是，在某些情况下(例如，服务所请求的后端系统或数据库不可用)，该服务可能会以错误消息作为响应。
InFaultPipe is invoked on the client side when the fault message is received; the OutFaultPipe is invoked on the server side when an invocation causes a fault to be sent to the client.
收到Fault消息后，在客户端调用InFaultPipe；如果某个调用导致将错误发送到客户端，则在服务器端调用OutFaultPipe。
However, note that if the payload is a SOAP Fault, then it's the user's responsibility to ensure that the Fault message is compatible with the selected SOAP version.
但是请注意，如果有效负载为SOAP错误，则确保错误消息与所选的SOAP版本兼容是用户的责任。
However, note that if the payload is a SOAP Fault, then it's the user's responsibility to ensure that the Fault message is compatible with the selected SOAP version.
但是请注意，如果有效负载为SOAP错误，则确保错误消息与所选的SOAP版本兼容是用户的责任。
应用推荐