>>Something like
>>
>><Body>
>><Fault>
>><faultcode>Server.Busy</faultcode>
>><faultstring>Too many connections</faultstring>
>><detail>you can be more specific here, including sub-elementing</detail>
>></Fault>
>></Body>
>>
>
>Based on the requirement of what I showed in the first message, I understand that I can wrap it with the Body root tag but can I use the layout as I described?
a) no
faults element;
b)
faultcode and
faultstring should be filled (there are a couple of standard codes for
faultcode, notably
Client - something wrong with Client request - and
Server - something wrong with server processing, such as lack of resources;
faultstring should be human-readable) - there is no point in reproducing these elements under the
detail element;
c) you can be more specific with the
detail section; for instance, in a debug environment, you could return the execution context (error code, line number, ...);
d)
faultactor is optional and I don't think it applies to this case (unless it happens to be a chain of SOAP messages);
>Also, doing as you say, will this generate an error on the client or this is just a standard way to send a smooth error assuming the client will verify for such content?
The client is responsable for error messages handling. It will generate an error at his side if he does it improperly ;)
----------------------------------
António Tavares Lopes
