Is my assumption correct that if i define a fault message in the portType.operation node, in the case of that fault, the fault.detail element will hold a node with the local name of the porType.operation.fault.name value?
If so - what happens if the porType.operation.fault.name is not given (that attribute is optional)?
Your assumption is not correct.
In an attempt to clarify, I'll give an example:
In the <wsdl:types> element in the WSDL of a web service, there is an element declaration:
In the WSDL, there is the following <wsdl:message>, <wsdl:portType> and <wsdl:binding> definitions:
Note that the <wsdl:fault> in the <wsdl:binding> element uses the name element to refer to the corresponding <wsdl:fault> element in the <wsdl:portType> element.
If the web service in question generates a fault, the SOAP message returned will look like this:
Note how the <detail> element contains the <addValuesFault> element, as defined in the <wsdl:types> section. The <addValuesFault> element, in turn, contains the three child elements <errorMsg>, <value1> and <value2> - again according to the definition of the <addValuesFault> element.
As far as I can tell, there is nothing specifying how to use the name attribute you ask about in the SOAP 1.1 or WSDL 1.1 specifications.
http://www.w3.org/TR/wsdl http://www.w3.org/TR/2000/NOTE-SOAP-20000508/ Best wishes!
posted 9 years ago
Many thanks for the great help!
expectation is the root of all heartache - shakespeare. tiny ad:
how do I do my own kindle-like thing - without amazon