Binding

This topic lists closed issues related to Binding.

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.