WSDL limitations for consumption

Most WSDL files are accepted during consumption, but some files can cause problems:

• SOAP-encoded arrays and SOAP-encoded structures are not supported. This means that RPC-encoded and document-encoded web services with complex input or output parameters do not work. For example, Amazon Web Services API and Google Web Services API fall into this category.
• All operations should be of one kind—that is, all RPC-encoded or all doc/literal.
• Only SOAP operations are considered. MIME and HTTP operations are ignored.
• Non-ASCII characters are not supported in SOAP UI  to create a Webservice client for by using the WSDL URL. SOAP supports only the following characters:
  !, *, -, _, ;, :, ~, $. 
  You can use other SOAP clients if you face issues with rendering the web service with special characters.
• Overloaded operations are not allowed.
• Both input and output should be present; one-way messaging is not allowed.

• A WSDL file cannot have both a <wsdl:include> and a <wsdl:types> element.

  Tip

  As a workaround, use <xsd:include> inside <wsdl:types>. There is no restriction on the number of <xsd:include> elements that you can use.

• A WSDL file cannot have more than one <wsdl:include> element.
• AR System supports Message Parts that point to XML Elements or XML Simple Types only.
• If a <wsdl:message> element has more than one Message Part, only the first Message Part is considered.
• Header in response (output mapping) is not supported.

Fetching records through a filter

When you import WSDL for consuming a web service, the WSDL shows an HTTP endpoint instead of an HTTPS endpoint. When you consume the WSDL with an HTTP header through a filter, no records are fetched.

After import of WSDL, modify the endpoint to https, and call the filter.

The following screenshot shows the updated endpoint: