This topic applies only to the IBM Business Automation Workflow Advanced
configuration.

Limitations of the HTTP binding

Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
The HTTP binding has the following limitations.

HTTPStreamDataBindingBytes data binding

This data binding requires that a request (and response for a two-way operation) service data object (SDO) be based on the shipped XML Schema Definition (XSD). If the SDO is not based on this XSD, an error is issued during validation. To add this XSD, that is, this business object, to your module, open the dependencies editor. Under Predefined Resources, select Native Body schema for Native Body Datahandler. Save your work and close the dependencies editor. In the navigation view under Data, the business object is listed.

Default content encoding with a POST operation

Default content encoding assumes an XML format is used. In a POST operation, this encoding will cause errors. You must specify a non-XML format such as text/plain.