Forum Discussion
MarcusJ
Staff
11 years agoHi,
The WSDL analyzer checks that the WSDL is syntactically valid as far as I know, and does not do WS-I compliance checking unless you can show that it does. The explanation for error code BP2402 based off what I have found is "The wsdl: binding element does not use a soapbind: binding element as defined in section "3 SOAP Binding." of the WSDL 1.1 specification". Not sure if that is valid for your WSDL or not. We do use an old version of the WS-I compliance check tool so you may find differences when doing WS-I compliance check from a different application.
Regards,
Marcus
SmartBear Support
The WSDL analyzer checks that the WSDL is syntactically valid as far as I know, and does not do WS-I compliance checking unless you can show that it does. The explanation for error code BP2402 based off what I have found is "The wsdl: binding element does not use a soapbind: binding element as defined in section "3 SOAP Binding." of the WSDL 1.1 specification". Not sure if that is valid for your WSDL or not. We do use an old version of the WS-I compliance check tool so you may find differences when doing WS-I compliance check from a different application.
Regards,
Marcus
SmartBear Support