Error while adding a SOAP host ..

[Naineyess]

Hello

I am trying to connect to a server by the SOAP plugin using WSDL and Whenever I am trigering the workflow "Add a soap host" I am getting an exception error as :-

Unable to load content of WSDL and its schemas! Reason: Unsupported encoding type: {http://schemas.xmlsoap.org/soap/encoding/}arrayType (Dynamic Script Module name : addSOAPHost#8)

Please help me to resolve this ..

Thank you.

[iiliev]

Hi,

If possible, could you attach your WSDL file?

Most likely, the issue is the WSDL type. I think SOAP plug-in supports only Document/literal and RPC/literal WSDL types, and it's possible that your WSDL file is of some unsupported type (e.g. RPC/encoded).

[Naineyess]

I am not very sure about the type so can you please explain lil more regarding this .. And what are the options to make it work ??

WSDL:-  https://localhost:8443/PAS/services/WSCentralService?wsdl

[iiliev]

Description of various WSDL styles is available on the net; see, for example, http://www.ibm.com/developerworks/library/ws-whichwsdl/

BTW, links to localhost are not very useful Could you save it as a file an attach it?

[Naineyess · Accepted solution]

Attached WSDL file

[igaydajiev]

Attached  WSDL file is in RPC/encoded style. and unfortunately this is not supported by SOAP pluign.

style="rpc"

use="encoded"

     <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
...
            <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://wscentralservice.services.dharma.iconclude.com" use="encoded"/>

Although it is legal WSDL, RPC/encoded is not WS-I compliant and is not supported by vCO SOAP plugin..

SOAP plugin supports only  Document/literal and RPC/literal see  'Supported WSDL style/use models' section in  https://www.vmware.com/support/orchestrator/doc/soap-plugin-103-release-notes.html

If you have control over the target web service you can regenerate the WSDL file in one of the supported formats.

In case you don't own the target web service  you can convert the WSDL manually. There are articles in the web explaining the exact rules http://wso2.com/library/knowledge-base/convert-rpc-encoded-wsdl-document-literal-wrapped-wsdl/