Limitations on WSDL Files

If you are having problems with the orchestration workflows in your process apps, it might be because the WSDL files you are using are not fully supported by SBM Composer. Although SBM Composer supports most WSDL files, it has some limitations. Contact your Web service provider to determine if any of the following restrictions apply:

• Only SOAP encoding may be used (not REST).
• Multi-part WSDL files are not supported.
• The WSDL must be WSI-BP (WS-I Basic Profile) compliant.
• The following binding styles are supported:
  • Document/Literal
  • Document/Encoded
  • RPC/Literal
  • RPC/Encoded
• HTTP binding is partially supported:
  • HTTP/POST is supported
  • HTTP/GET is not supported
• Attachments are not supported.
• Recursive elements or types cannot be imported into an application; however, you can import a WSDL that contains recursive elements into an orchestration workflow.
• Derived complex types are not completely supported in application workflows; however, they can be used in orchestration workflows.
• Operation overloading, where the same name can apply to different operations in different situations, is not supported.
• Attribute references are not completely supported.
• WSDLs might fail to import if they are not formatted correctly, or if they contain functionality that is not supported by SBM Composer.
• The <choice> element is not supported.

• Creating a base type in SBM Composer and then overriding it with any of its Extension types is not supported.

  For example, when you create "SearchRecord" in the following sample code, you get a child element named "record" of type "sObject". If this type is extended by other types, such as "Employee" or "Hardware", you will not be able to change the type of "record" to "Employee" type on the Data Mapping tab of the orchestration workflow Property Editor. You can, however, create a working data element of type "Employee".

  <complexType name="SearchRecord">
  <sequence>
  <element name="record" type="ens:sObject"/>
  </sequence>
  </complexType>

• Creating arrays of varying lengths as Web service inputs is not supported. For example, you can create an array on the Data Mapping tab of the orchestration workflow Property Editor if you know how many records to create. However, if you are unable to determine the number of records at design time, SBM cannot create such an array.
• All WSDL definitions (wsdl:service, wsdl:binding, wsdl:portType, wsdl:message, and wsdl:types) must be in the same namespace; splitting WSDL definitions into more than one namespace is not supported, even if wsdl:import is used. However, the XSD schemas that are declared or imported into the wsdl:types section can be in namespaces that are different from the WSDL definitions namespace.