What are the limitations of the WSDL file in Salesforce?

Hello chanchal,

Limitations of WSDL file are:

1. A WSDL file cannot have both a <wsdl:include> and a <wsdl:types> element but you can use  <xsd:include> inside <wsdl:types>.
2.  A WSDL file cannot have more than one <wsdl:include> element.
3.  Only SOAP operations are considered in WSDL file.
4. All MIME and HTTP operations are ignored during consumption.

Hi,

Mapping Headers
Headers defined in the WSDL document become public fields on the stub in the generated class. This is similar to how the AJAX Toolkit and .NET works.
Understanding Runtime Events
The following checks are performed when Apex code is making a callout to an external service.

• For information on the timeout limits when making an HTTP request or a Web services call, see Callout Limits and Limitations.
• Circular references in Apex classes are not allowed.
• More than one loopback connection to Salesforce domains is not allowed.
• To allow an endpoint to be accessed, register it from Setup by entering Remote Site Settings in the Quick Find box, then selecting Remote Site Settings.
• To prevent database connections from being held up, no transactions can be open.

Understanding Unsupported Characters in Variable Names
A WSDL file can include an element name that is not allowed in an Apex variable name. The following rules apply when generating Apex variable names from a WSDL file:

• If the first character of an element name is not alphabetic, an x character is prepended to the generated Apex variable name.
• If the last character of an element name is not allowed in an Apex variable name, an x character is appended to the generated Apex variable name.
• If an element name contains a character that is not allowed in an Apex variable name, the character is replaced with an underscore (_) character.
• If an element name contains two characters in a row that are not allowed in an Apex variable name, the first character is replaced with an underscore (_) character and the second one is replaced with an x character. This avoids generating a variable name with two successive underscores, which is not allowed in Apex.
• Suppose you have an operation that takes two parameters, a_ and a_x. The generated Apex has two variables, both named a_x. The class doesn’t compile. Manually edit the Apex and change one of the variable names.

Hope this helps.