MuleSoft · Web Service Consumer Connector
WSC:INVALID_WSDL
Short answer
WSC:INVALID_WSDL means the WSDL is poorly formatted. Validate the WSDL in a viewer and, if it is loaded from a remote host, confirm the app can reach that host.
VerifiedLast verified
01Error text
Error type: WSC:INVALID_WSDL02Likely causes
- The WSDL is poorly formatted.
- At design time, WSDL errors also show up as missing metadata, an empty Operations field, or Port and Address not filled in automatically.
03How to fix it
- Check the WSDL with a WSDL viewer.
- If the WSDL is not in
src/main/resources, check connectivity to the host that serves it. - If the WSDL host needs authentication, configure custom HTTP settings for it.
- Handle the failure with an error handler of type
WSC:INVALID_WSDL.
04Official documentation
→Related errors
- WSC:BAD_REQUESTWSC:BAD_REQUEST means the operation does not exist in the WSDL, or the request body is not valid XML. Pick an operation the WSDL defines and build the body as well-formed XML.
- WSC:CANNOT_DISPATCHWSC:CANNOT_DISPATCH is raised when the request cannot be dispatched and the HTTP error cannot be turned into a SOAP fault. In version 3.0 that covers one-way operations, WSDL or schema requests, an empty HTTP error body, or an error body over 1048576 bytes.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer