SOAP bindings error when you drag a WSDL file onto Message
Flow editor
Procedure
Scenario: You drag a WSDL file, that was generated
when you created an MQ Service, onto
the Message Flow editor. A window opens that contains the error, 'There
are no imported SOAP bindings in the WSDL file'.
Explanation: IBM® Integration Toolkit expects
WSDL files to contain SOAP bindings, but the WSDLs that an MQ Service generates do not contain SOAP
bindings.
Solution: The WSDL files that the MQ Service generates are valid. Creating
a node by using an MQ Service WSDL
file is not supported. To create an MQ node, drag the MQ Service, rather than the WSDL file,
onto the Message Flow editor.
SOAP bindings warning in Problems view when an MQ Service generates
a WSDL
Procedure
Scenario: You create an MQ Service, and that generates a WSDL file.
The Problems view displays the warning, 'The Service does not contain
any binding that uses a SOAP 1.1 binding'.
Explanation: The validator expects WSDL files to
contain SOAP bindings, and deems a WSDL file invalid if it does not
contain them. However, not all WSDL files require SOAP bindings. The
WSDL files that an MQ Service generates
do not contain SOAP bindings, and are valid.
Solution:
Click Window > Preferences.
In the Preferences window, open Integration
Development > WSDL > Validation.
Check the Allow Services that contain non-SOAP bindings
check box and click Apply.