We are excited to release Exchange Framework (TIF) v1.5.0 with the following key features:
A standard integration fluent function base class
This base class provides the most commonly used code for a typical integration fluent function. The code pattern in this class has passed hundreds of regression test cases providing a reliable foundation that saves you time and lets you focus on your specific project code.
A powerful standard response processor out of the box
Previously, you needed to create a response processor subclass and write code to process the raw response field by field, and generate Server VO and Client VO manually. From Exchange Framework v1.4.0, we started to provide simple annotation to let a response processor inject certain values from the raw response into the Server VO automatically.
Exchange Framework v1.5.0 takes this further with additional auto response processing capability, providing a fully working response processor out of the box that saves time parsing the response manually.
Exchange Framework v1.5.0 dramatically reduces the code required to create your main fluent function and to parse raw responses. We strongly encourage everyone to upgrade and start using Exchange Framework v1.5.0 to build your next powerful integration.
More details
For full details, refer to the Exchange Framework 1.5.0. If you have trouble accessing the project, contact
The latest v1.6.1 of the Exchange Framework (TIF) has now also been released
We are pleased to add the built-in configuration service support in this release so that your fluent function using TIF will automatically be compatible with the configuration service with the following features without any extra code:
- Triggers the specified configuration service on demand.
- Uses the config data from the configuration service if available, otherwise fall back to the original service connection and service parameters from the service definition and make those up-to-date config data available to your fluent function.
Other updates to the Exchange Framework in this release include:
- Provide the capability to disable the Journey Analytics milestones in the Fluent function base class.
- Add capitalized Key annotation to match the capitalized tag name convention in Txn XML that generated by Server VO/Client VO (default is true)
- Add get and create form/organisation property in Utils class
- Add request object access in the base fluent function
- Support mocking a Groovy service or fluent function in MockUtils
- Support mocking a GET request in MockUtils
- Fix a minor issue in Utils.exceptionToString() method