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: Same as 1 except for removing type encoding info from soap messages, 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 cocould be multiple children not complying to WS-I
5. dcoument/literal wrapper
This method is usually used.
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 between des operation name, soap: body only includes des one child complying to WS-I, but not supporting Java overload