Binding

This topic lists closed issues related to Binding.

Release 6.10.0

Key Summary
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.
BWCE-6100 From a REST service with POST operation having Content-Type as "application/json", if the JSON formatted text contents are sent to the REST client in response, then it is 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"}.

Release 6.9.1

Key Summary
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 6.9.0

Key Summary
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 ActiveMatrix BusinessWorks™ 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"}

Release 6.8.1

Key Summary
AMBW-45639

When Invoke activity with REST Reference binding is configured with absolute file path for multipart form parameters, it deletes the files that are 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".
AMBW-45155

The 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 6.8.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.

Release 6.7.0

Key Summary
AMBW-41468 After migration, the org.apache.axiom.om.OMException: Unable to determine SOAP version error occurred when an attachment style was MTOM.

Add the following property:

bw.binding.soap.client.reply.mtom.contenttype.override=true.

AMBW-41299 The unbound header parts were missing in the concrete WSDL generated at design time using the Generate Concrete WSDL option from SOAP service, which imported another WSDL importing request and response header XSDs.
AMBW-41129 The Apache Axis2 threads were not increased with an increase in load.
AMBW-40680 The Unbound Header parts were missing in the runtime concrete WSDL retrieved from SOAP service with version 1.2.
AMBW-40679 The Unbound Header parts were missing in the runtime concrete WSDL retrieved from a SOAP service when the abstract WSDL imported another WSDL, and the WSDL imported request and response header XSDs.
AMBW-40484 The Send HTTP Request activity could not send the request with Content-type as multipart/form-data to ServiceNow with Apache HttpComponents library.

Send the POST request using the Jetty HTTP Client library in the HTTP Client shared resource.

AMBW-39997 The incorrect error code 403 Forbidden was thrown for the Invoke activity in a SOAP over HTTP application when the HTTP Client shared resource was configured with the following options:
  • Default port = 443
  • Implementation Library = Apache HttpComponents(Supported by HTTP 1, SOAP and REST)
  • Default Confidentiality check box was selected.
AMBW-39819 The time required for runtime concrete WSDL retrieval for a SOAP service increased if more applications with a large number of schemas were deployed on the same AppNode.
AMBW-39038 The runtime concrete WSDL took too much time to generate when an endpoint was hit in the browser, because the schema cache was not initialized before WSDL retrieval.