- Posts: 358
- Joined: Fri Nov 29, 2013 8:26 pm
SOAP 1.1 allows using dot in faultcode, such as soap.Server.ProcessingError.
SOAP 1.2 disallows the dot.
BP 1.1 discourages the future use of the dot.
So, is soap.Sever.ProcessingError still BP 1.1 conformant?
- Posts: 429
- Joined: Tue Jul 24, 2012 2:43 am
No, it isn't.soap.Sever.ProcessingError
What they are trying to say is with this rule:
adn this sentence:R1004 When an ENVELOPE contains a faultcode element, the content of that element SHOULD be either one of the fault codes defined in SOAP 1.1 (supplying additional information if necessary in the detail element), or a Qname whose namespace is controlled by the fault's specifying authority (in that order of preference).
is that the dot has already been used in the situation where the namespace (e.g. "http://example.org/faultcodes") is controlled by another authority, for instance:A number of specifications have already defined custom fault codes using the "." (dot) notation. Despite this, their use in future specifications is discouraged.
Code: Select all
<soap:Fault xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/' xmlns:c='http://example.org/faultcodes' > <faultcode>c:ProcessingError.algorithm.encrypt</faultcode> <faultstring>An error occured while processing the message</faultstring> </soap:Fault>
Code: Select all
<soap:Fault xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/' xmlns:c='http://example.org/faultcodes' > <faultcode>c:ProcessingAlgorithmEncryptError</faultcode> <faultstring>An error occured while processing the message</faultstring> </soap:Fault>
Regards,R1031 When an ENVELOPE contains a faultcode element the content of that element SHOULD NOT use of the SOAP 1.1 "dot" notation to refine the meaning of the fault.
- Posts: 124
- Joined: Wed Feb 12, 2014 2:44 am
If the server determines that information in the client SOAP header is invalid and generates a SOAP fault. What is the appropriate fault code for this type of SOAP fault?
It should be client or must-understand ?
Users browsing this forum: No registered users and 1 guest