Binding

This topic lists closed issues related to Binding.

Release 2.10.0

Key Summary
BWCE-7842

TIBCO Business Studio for BusinessWorks goes into a non-responsive state when trying to drag-n-drop operations into a process file to create a REST service.

BWCE-7086

In a REST service with anyType element at the root an error is thrown at runtime.

Now support is added for creating REST service with any element as root and to apply its effect at runtime set the system property bw.rest.binding.resp.allowwildcard.inschemaroot=true in the VM arguments.

A couple of caveats:

  1. At designtime, the validation error The wildcard elements/attributes are not permitted in the element occurs.

  2. The solution will work only when the element root in the schema configured for the REST service is a wildcard. The solution won't work if one or more elements in the schema are wildcards and some aren't.

BWCE-6805

The REST Invoke activity with reference binding fails with the error java.lang.RuntimeException: Cannot initialize a message part with a null value, if a service responds with Content-Type other than application/json.

AMBW-51188 For undeclared faults, you now have a choice schema option of "message" or "fault actor, fault string, and fault code" at the input.
AMBW-51162 Swagger UI fails to load giving a "java.lang.NullPointerException" when the design time Swagger file is either deleted or manually renamed in the project containing a REST service.
AMBW-51053 The XSD generated from a Swagger file containing only the "minimum" keyword for integer type element has a validation error at design time since the maxInclusive restriction is getting added with a "null" value.
AMBW-50934 SOAP reference binding's output XML validation fails with an application-level system property.
AMBW-50641 The BusinessWorks application with REST service fails with a 500 error when the Use HTTP Header checkbox is selected and Content-Type is provided in the Input tab of the Reply activity.
AMBW-50639 The "charset" is getting added along with the Content-type in the response header on invoking a REST service.

Now the charset is not added by default. The charset can be present in the response header content-type by setting the property "bw.rest.autoAppendCharsetToMediaType=true" in the TIBCO Business Studio for BusinessWorks VM arguments or the config.ini file of the AppNode.

AMBW-50632 Behavior differences are observed in ActiveMatrix BusinessWorks versions 6.7.x and 6.9.1 for a bad SOAP response.
AMBW-49956 An error "TIBCO-BW-CORE-500061: Reply activity error. The reply activity encountered an error on sending the response to the caller of this process." is thrown at runtime when trying to invoke an OAS 3.0 REST service operation configured with no response body.
AMBW-40923 The methods selected in the Disable HTTP Methods field of HTTP Connector shared resource configured with a REST service are still visible in the "Access-Control-Allow-Methods" response header when invoking the service.
AMBW-33406 You can now send a request to a REST service replying with Content-type as "text/xml" when the XML Format checkbox is selected in the Request tab of REST service binding.
AMBW-30360 An error, "The property called 'xxxxx' contains neither a 'type' nor '$ref' property, which is not supported" is thrown at design time while trying to Generate XSD from a Swagger file.
AMBW-29949 A "NullPointerException" is thrown while trying to generate XSD Schema using Swagger 2.0 JSON file having parameters defined with $ref.

Release 2.9.2

Key Summary
BWCE-7558

The Connection pool shut down error is observed at runtime if the Authentication checkbox is enabled in the HTTP Client Resource of REST Reference Binding.

BWCE-7516

If a request was sent to a REST service with property name starting with "xmlString" then at runtime the value for this property does not reflect.

AMBW-50724

An error, The property called 'xxxxx' contains neither a 'type' nor '$ref' property, which is not supported. is thrown at design time while trying to create a REST Service or Generate XSD Schema from a Swagger file.

AMBW-50631

Behavior differences are observed in ActiveMatrix BuisnessWorks version 6.7.x and 6.9.1 for a bad SOAP response.

Release 2.9.1

Key Summary
BWCE-6730

When you try to retrieve concrete wsdl, the "?wsdl" operation does not work after the endpoint and an exception occurs.

BWCE-2048

When invoking a REST service, the CORS headers are exposed in the response. To disable this behavior, pass the "-Dbw.rest.disable.cors.headers=true" system property in the VM arguments. Additionally, you can pass another property, "bw.access.control.allow.origin.cors.header.url" for allowing requests from the specific origin (such as Swagger). For example, "-Dbw.access.control.allow.origin.cors.header.url=http://<hostname>:7777". This property takes effect only when the property for disabling CORS headers (bw.rest.disable.cors.headers) is set to true.

AMBW-49847

An error occurs when there are multiple schemas with no namespace in the same module or Shared module.

AMBW-49846

An error occurs when there are two schemas with the same namespace in the same module or Shared module.

AMBW-49706

High CPU usage is observed when processing a 24 MB file in SOAP activity.

AMBW-49637

A "String length exceeds the maximum length" error is thrown when invoking a REST service with a large JSON file as Input for POST operation.

AMBW-50556

An error TIBCO-BW-CORE-500061: Reply activity error. The reply activity encountered an error on sending the response to the caller of this process. is thrown at runtime when trying to invoke an OAS 3.0 REST service operation configured with no response body.

AMBW-50554

The "description" provided in the Swagger file does not reflect in the Swagger UI when the REST service is invoked.

Now when a top-down REST service is invoked using a Swagger file having a "description" provided for operation, its Request and Response objects, and its individual properties, the same is reflected in the Swagger UI.

Release 2.9.0

Key Summary
BWCE-6162

The root namespace is replaced with child element namespace in the response received from a REST service.

BWCE-5087

The response schema for 201 status code is not reflecting in the Invoke activity on creating a REST reference binding from an OAS 3.0 swagger file which had 201 as a success response status code instead of 200.

AMBW-49116 Duplicate authorization has now been removed from the TCP trace.
AMBW-48942 When a REST service is invoked with invalid Query/Path parameters, the Catch All block in the service is not executed.
AMBW-48936 The attributes that are present at the root element level are missing in the output of Invoke activity while invoking a REST service having XML as the response content type.
AMBW-48920 Unable to retrieve WSDL in ActiveMatrix BusinessWorks version 6.9.0 for the attached project.
AMBW-48638 The expected JSON response is not obtained in the following cases:
  • An array of strings has only one element, which is set explicitly to "nil" and the Use Empty Values for Null checkbox in the REST Service Binding response tab is selected.

  • The array of strings and array of objects have only one element set to "nil", and the Use Empty Values for Null checkbox is unselected.

Both the scenarios give expected results now. For the second scenario, set the com.tibco.bw.restjson.array.null=true property in the VM arguments of TIBCO Business Studio for BusinessWorks to get the expected result.

AMBW-38146 The Content-Type header set in the Input tab of REST Reference binding's Invoke activity is not reflecting at runtime.
AMBW-32475 When "Null" as an input value is passed for some of the elements in a REST service, it is converted to an empty value in the output.

Release 2.8.3

Key Summary
BWCE-5908

When a REST Service is invoked with an invalid Query or Path parameters, the Catch All block in the service is not executed.

BWCE-5811

When REST Applications are deployed on container where SSL is configured from the outside rather than configuring it within the application, the Swagger UI does not load due to the protocol mismatch error.

A new property bw.rest.enable.secure.swagger.url is added to switch the Swagger URL protocol to HTTPS when the property is set to true to resolve this issue.

BWCE-5767

From a REST service with POST operation having Content-Type as "application/json" , if the JSON formatted text contents were sent to the REST client in response, then it was being received as normal text instead of JSON formatted contents.

Note: If an invalid JSON which is a simple string is provided in the response, the Swagger UI shows a parsing-related error, can't parse JSON. Raw result: along with the response value; which is the expected behavior. The response value must be configured with the correct JSON format. For example, {"name": "abc"}
BWCE-5289

The java.io.IOException error occurs on running an application having the REST Reference Binding in Binary Shared Module.

AMBW-48261

The attributes that are present at the root element level are missing in the output of Invoke activity while invoking a REST service having XML as the response content type.

AMBW-48196

When a REST service is invoked with invalid Query/Path parameters, the Catch All block in the service is not executed.

Release 2.8.2

Key Summary
BWCE-5375

On invoking a REST service using REST reference binding, if a fault is received in response then its failing with NullPointerException instead of giving the proper fault data.

AMBW-48168 When migrating TIBCO ActiveMatrix BusinessWorks 5.x SOAP project to 6.x, the input mappings on the Invoke activity are lost, causing an issue while invoking the SOAP service.
Note: The input of the "_configData" element from the ActiveMatrix BusinessWorks 5 project must be provided as an input in the SOAP Reference Binding -> Request Context -> endpointURI field.
AMBW-48167 An error "TIBCO-BW-FRWK-400030: Error destroying binding [RestService1], <CausedBy> java.lang.NullPointerException" is thrown after the application restart when some changes are made to an already running application having multiple REST services with similar resource service paths.
AMBW-48157 The anyType element in the input editor of the SOAP service, which is expected to receive any kind of requested XSD data structure is not mapping the received data in any element, resulting in an empty output from OnMessageStart.
AMBW-48028 The Error Code is not reflected in the FaultDetails/MsgCode element when a REST service fails due to a bad request.
AMBW-48017 Data types are missing during the Generation of XSD from the Swagger file containing JSON schema object with properties referring to other models.
AMBW-47607 To address security vulnerabilities in the snakeyaml-1.33.jar file, the SnakeYAML jar has been updated to version 2.0.

Release 2.8.1

Key Summary
BWCE-5136

The attachments sent to a REST Service with multiple/form-Data-Content-type is saved in the temp folder causing disk space errors.

BWCE-4889

An input is required for OPTIONS operations of a REST Service implemented as Opaque, when invoked from Swagger UI.

AMBW-47555

When invoking a REST service without Policy configured on the binding, the Username and Password fields are not visible in the Swagger UI. To make the fields available in Swagger UI, set the property -Dbw.rest.swaggerui.legacy.basicauth.enable=true in the VM arguments of TIBCO Business Studio for BusinessWorks or a config.ini file of appnode.

Note: If the REST service has a Policy configured on the binding as well as the above property is set to true, then the preference is given to the credentials passed from the Authorize button.

AMBW-47514

The "charset" gets added along with the Content-type in the response header on invoking a REST service.
Now, the charset is not added by default. The charset can be present in the response header content-type by setting the property bw.rest.autoAppendCharsetToMediaType=true in the TIBCO Business Studio for BusinessWorks VM arguments or the config.ini file of the appnode.

AMBW-47419

Status code 400 is not handled correctly in one-way SOAP invocation.

AMBW-47154 If multiple REST services (endpoints) are part of the same process and the Reply activity is configured to reply with 400 faults, then on invoking the service, the Fault message does not display for the client.

Release 2.8.0

Key Summary
BWCE-4854 When the Invoke activity with reference binding is used to send multipart/form-data of File/Text type to a REST service, a FormFileException exception is thrown only on docker.
AMBW-46622

Invoking SOAP service fails with "Failed to initialize SoapReferenceBinding - TIBCO-BW-SCHEMA-RESOLVER-500201: WSDL not found" error.

AMBW-46604

The ProcessStack field under the FaultDetails tab is not populating the correct Process Name in the fault details when the process has two service bindings with the same operation.

AMBW-46557

The XML parser in TIBCO BusinessWorks™ Container Edition does not recognize the boolean value and treats it as a whitespace.

AMBW-46371

On installing TIBCO ActiveMatrix BusinessWorks™ 6.7.0 HF-005, whitespaces are getting trimmed in the output.

AMBW-46046

When a process has multiple reference bindings with "Enable DefaultFaultElement" and "Enable CustomFaultElement" selected ONLY in one of the bindings, the fault in the Catch block throws design-time errors.

AMBW-22981

When invoking a REST service's GET operation with Content-Type as "application/json" having response as "string" type, the response content-type changes to "text/plain".

Note: If an invalid JSON i.e. a simple string is provided in the response, the Swagger UI shows a parsing-related error, "can't parse JSON. Raw result:" along with the response value; which is the expected behavior. The response value must be configured with the correct JSON format, for example:

{"name": "abc"}

AMBW-47033

The SOAP service returns xml:lang="en_US" instead of xml:lang="en-US" in the fault response under <soapenv:Reason>.

AMBW-46818 When TIBCO ActiveMatrix BusinessWorks 6.x exposes SOAP service over the service binding with the MTOM attachment style selected, it returns the attachments as SwA (SOAP with Attachments)

Release 2.7.3

Key Summary
BWCE-4754 The SOAP fault returns HTTP Status Code as 200 instead of 500.
AMBW-46477 Invoking SOAP service fails with Failed to initialize SoapReferenceBinding - TIBCO-BW-SCHEMA-RESOLVER-500201: WSDL not found error.
AMBW-46009 The ProcessStack field under the FaultDetails tab is not populating the correct Process Name in the fault details when the process has two service bindings with the same operation.

Release 2.7.2

Key Summary
AMBW-45639

When Invoke activity with REST Reference binding was configured with absolute file path for multipart form parameters, it deleted the files that were passed as mimePart input .

AMBW-45520

For bypassing the version validation in TIBCO Business Studio for BusinessWorks for swagger files having openapi version other than 3.0.0, pass the property bw.plugin.rest.disableOpenApi3xVersionValidation=true in the TIBCOBusinessStudio.ini file.

AMBW-45399 The application fails to start intermittently and throws an error "TIBCO-BW-SCHEMA-RESOLVER-500201: WSDL not found".
AMBER-45155

Runtime Swagger file does not include enumeration restrictions which are defined in a request and response XSD configured with the REST service.

AMBW-45154 The Runtime Swagger file of a REST service has optional extension elements declared in the XSD as required.
AMBW-45153 The Runtime Swagger file does not include field length restrictions which are defined in a request and response XSD configured with the REST service.
AMBW-43403

The XSD generation, and Service or Reference binding creation operation are no more blocked, by avoiding parsing of "#/components/examples".

Release 2.7.0

Key Summary
AMBW-43816

For REST application deployed on an AppNode, the bw-flowlimit-executor-provider threads are not destroyed and keep on increasing even after starting and stopping an application.

AMBW-43397

You can now decide whether to send SOAP headers or not in the SOAP Envelope of the service. Set the -Dbw.binding.soap.client.invoke.send.headers property as a VM argument in TIBCO Business Studio for BusinessWorks or in the config.ini file to false to stop sending SOAP headers.

By default, the property value is set as true.

AMBW-43238

Empty header is passed in response in the SOAP envelope even if you don't configure the SOAP service with Headers.

To not send empty headers set the property bw.binding.soap.client.reply.empty.header.override=true.

AMBW-42775 The "definitions" section in the runtime Swagger file does not show the type as "array" for the child properties of an object when you run a REST service configured with a complex element in an XSD, and the element's definition in the XSD contains <xs:extension> element with base attribute and array-based sub-elements.
AMBW-42550 The operationID field is now displayed in the runtime Swagger file of a REST service when it is hit from Swagger UI.
AMBW-42313

The Configure Local Swagger option does not work when you import a project in TIBCO Business Studio for BusinessWorks first and then configure the Local Folder path in the API Explorer tab.

AMBW-27634

The null pointer exception is thrown while adding the SOAP Unbound Headers.