A WSDL service contract differs from the XSD in that it defines both invocation payload and protocol. It is the easiest as well as the most common way to integrate with a Web Services Server. The WSDL file defines a complete interface, including:
Corticon Server SOAP binding parameters.
Decision Service Name.
Payload, or XML data elements required inside the request message (this portion of the WSDL is identical to the XSD).
XML data elements provided within the response message.
The Web Services standard allows for two messaging styles between services and their consumers: RPC-style and Document-style. Document-style, sometimes also called Message-style, interactions are more suitable for Decision Service consumption because of the richness and (potential) complexity common in business. RPC-style interactions are more suitable for simple services that require a fixed parameter list and return a single result. As a result,
Important: Corticon Decision Service WSDLs are always Document-style! If you intend to use a commercially available software toolset to import WSDL documents and generate request messages, be sure the toolset contains support for Document-style WSDLs.
For more information on WSDL, see http://www.w3schools.com/webservices/ws_wsdl_intro.asp
Corticon Server SOAP binding parameters.