WSDL binding style for SOAP

 A Web Services Description Language (WSDL) binding style can be RPC or document. The use can be encoded or literal. The  combination of style and use  can be:

1.  RPC/encoded

2.  RPC/literal

3.  Document/encoded

4.  Document/literal

5.  Dcoument/literal wrapper

 

 

1.  RPC/encoded

 

feature: straightforward description, operation name in the message, there are type encoding info in the message,but not easily validation cause not all defined in the schema, not WS-I compliant

 

2.  RPC/literal

feature: 与1相同除了soap消息中移除了type encoding info, WS-I compliant

 

3. Document/encoded

feature: not WS-I compliant

 

4. Document/literal

feature: no type encoding info in message, everything within soap:body defined in schema leads to easily validation,but operation name not occurring in message, soap:body could be multiple children not complying to WS-I

 

5.  Dcoument/literal wrapper

该种方式用的比较多。

These are the basic characteristics of the document/literal wrapped pattern:

• The input message has a single part.
• The part is an element.
• The element has the same name as the operation.
• The element's complex type has no attributes.

feature: no type encoding info in message, everything defined in schema, message includes operation name, soap:body only includes one child complying to WS-I, but not supporting java overload