I/O Docs WSDL requirements

As with all things SOAP, things can sometimes get complicated quickly. We did our best to adapt to common practices for WS-Security, Schemas, and Types, but there are  a few “rules of the road” to using WSDLs to generate I/O Docs. These guidelines are broken into three sections: Unsupported WSDL elements, Suppported WSDL extension namespaces, and WSDL element restrictions.  This page will continue to be updated - please check here often. 

WSDL Version

WSDL version 1.1 is supported, other WSDL versions not supported at this time. For services using other WSDL versions, first convert to WSDL 1.1 format if possible. 

Unsupported WSDL elements

- /definitions/import element

• External namespaces will NOT be imported to the WSDL using WSDL import feature, however, the /definitions/types/schema element can use xml schema import for types defined externally

Supported WSDL binding extension namespace

• soap 1.1:  http://schemas.xmlsoap.org/wsdl/soap/
• soap 1.2: http://schemas.xmlsoap.org/wsdl/soap12/
• http: http://schemas.xmlsoap.org/wsdl/http/

WSDL element Restrictions

The converter will ignore any WSDL elements that do not meet these restrictions.

 /definitions element

• must have at least but no more than ONE service element.
• must contain zero or one types element
• must contain one or more binding elements
• must contain one or more portType elements
• must contain one or more message elements

 /definitions/types element

• must contain one or more schema element from the namespace http://www.w3.org/2001/XMLSchema

 /definitions/service element

• must contain one or more port elements

 /definitions/service/port elements

• must contain a single address element from the supported WSDL binding extension namespaces
• binding attribute must refer to a binding defined within the WSDL file

 /definitions/binding elements

• must contain a single binding element from the supported WSDL binding extension namespaces
• type attribute must refer to a portType defined within the WSDL file
• must contain one or more operation elements

 /definitions/binding/operation elements

• must contain a single operation element from the supported WSDL binding extension namespaces

SOAP 1.1 and 1.2

• must use document style bindings and binding operations (document style is default when not specified)

HTTP

GET

• must use urlEncoded for operation input
• urlReplacement not yet supported

POST

• must use a http://schemas.xmlsoap.org/wsdl/mime/ content type for operation input. example: application/x-www-form-urlencoded, text/xml, application/xml, application/json