About Question enthuware.ocejws.v6.2.53 :

Moderators: Site Manager, fjwalraven

Post Reply
himaiMinh
Posts: 358
Joined: Fri Nov 29, 2013 8:26 pm
Contact:

About Question enthuware.ocejws.v6.2.53 :

Post by himaiMinh » Fri Apr 11, 2014 7:35 pm

According to the explanation,
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?

fjwalraven
Posts: 429
Joined: Tue Jul 24, 2012 2:43 am
Contact:

Re: About Question enthuware.ocejws.v6.2.53 :

Post by fjwalraven » Sun Apr 13, 2014 1:11 am

soap.Sever.ProcessingError
No, it isn't.

What they are trying to say is with this rule:
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).
adn this sentence:
A number of specifications have already defined custom fault codes using the "." (dot) notation. Despite this, their use in future specifications is discouraged.
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:

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>
However they should change it (i.e. remove the dot) in their next release to be BP compliant. For instance:

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>
Then they will be in line with the following rule:
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.
Regards,
Frits

ramy6_1
Posts: 124
Joined: Wed Feb 12, 2014 2:44 am
Contact:

Re: About Question enthuware.ocejws.v6.2.53 :

Post by ramy6_1 » Thu Nov 05, 2015 9:46 am

Hello ,

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 ?

fjwalraven
Posts: 429
Joined: Tue Jul 24, 2012 2:43 am
Contact:

Re: About Question enthuware.ocejws.v6.2.53 :

Post by fjwalraven » Fri Nov 06, 2015 1:18 am

Hi,

That will be Soap:client.

Soap:mustUnderstand is typically returned if the server doesn't have a handler to process the mandatory header.

Regards,
Frits

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 3 guests