Complex XSD Constructs Mapping Rules

If backend services are using complex XSD constructs for WSDL operation signatures, such as multiple parts with complex types, you can use a mediation component between the Implementation Type for REST component and the backend component.

Follow these rules when mapping WSDL operation arguments (message parts) to HTTP operations.

  • Multi-part Operation
    • Simple types, or built-in simple XSD types such as string, float, boolean, integer and so on, must be passed as query or path parameters.
    • The name of the query parameter or path parameter must match the part name
    • Complex types, such as xsd:complexType must be passed as HTTP body

      TIBCO ActiveMatrix Binding Type for REST supports backend WSDL operations with only one part of complexType in the operation signature for multipart WSDL Executing the MultipleComplexTypes Sample illustrates how to use mediation to expose a multi-part WSDL to REST clients.

  • Single-part Operation
    • Simple types, or built-in simple XSD types such as string, float, boolean, integer and so on, must be passed as query or path parameters.
    • Complex types, such as xsd:complexType must be passed as HTTP body.