WS-I Basic Profile Version 1.1 - instructional media + magic
WS-I Basic Profile Version 1.1 - instructional media + magic
WS-I Basic Profile Version 1.1 - instructional media + magic
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
R2725 If an INSTANCE receives an envelope that is inconsistent with its <strong>WS</strong>DL<br />
description, it MUST check for "<strong>Version</strong>Mismatch", "MustUnderstand" and "Client" fault<br />
conditions in that order.<br />
4.7.19 Response Wrappers<br />
<strong>WS</strong>DL <strong>1.1</strong> Section 3.5 could be interpreted to mean the RPC response wrapper<br />
element must be named identical to the name of the wsdl:operation.<br />
R2729 An ENVELOPE described with an rpc-literal binding that is a response MUST<br />
have a wrapper element whose name is the corresponding wsdl:operation name suffixed<br />
with the string "Response".<br />
4.7.20 Part Accessors<br />
For rpc-literal envelopes, <strong>WS</strong>DL <strong>1.1</strong> is not clear what namespace, if any, the accessor<br />
elements for parameters and return value are a part of. Different implementations make<br />
different choices, leading to interoperability problems.<br />
R2735 An ENVELOPE described with an rpc-literal binding MUST place the part<br />
accessor elements for parameters and return value in no namespace.<br />
R2755 The part accessor elements in a MESSAGE described with an rpc-literal binding<br />
MUST have a local name of the same value as the name attribute of the corresponding<br />
wsdl:part element.<br />
Settling on one alternative is crucial to achieving interoperability. The <strong>Profile</strong> places the<br />
part accessor elements in no namespace as doing so is simple, covers all cases, and<br />
does not lead to logical inconsistency.<br />
4.7.21 Namespaces for Children of Part Accessors<br />
For rpc-literal envelopes, <strong>WS</strong>DL <strong>1.1</strong> is not clear on what the correct namespace<br />
qualification is for the child elements of the part accessor elements when the<br />
corresponding abstract parts are defined to be of types from a different namespace than<br />
the targetNamespace of the <strong>WS</strong>DL description for the abstract parts.<br />
R2737 An ENVELOPE described with an rpc-literal binding MUST namespace qualify<br />
the descendents of part accessor elements for the parameters and the return value, as<br />
defined by the schema in which the part accessor types are defined.<br />
<strong>WS</strong>DL <strong>1.1</strong> Section 3.5 states: "The part names, types and value of the namespace<br />
attribute are all inputs to the encoding, although the namespace attribute only applies to<br />
content not explicitly defined by the abstract types."<br />
From www.ws-i.org/<strong>Profile</strong>s/<strong>Basic</strong><strong>Profile</strong>-<strong>1.1</strong>.html 46 8 February 2008