Changelog

We’ve fixed an issue in SDKs where HTTP redirections were not being handled properly. Please generate new SDKs to receive the fixes.

We’ve added logging to our Java SDKs. Logging-enabled SDKs will log important events in the API lifecycle for troubleshooting or debugging later.

Both versions of RAML (0.8, 1.0) support XML examples and XML schema definitions. Previously, we supported only JSON examples and JSON schema definitions found in RAML input files. Now, however, we support parsing of XML examples and XML schema definitions as well.

We’ve updated our SDKs that use OAuth 2 Client Credential Flow to enable automatic re-authorization of the client when the OAuth token is expired.

We’ve added the ability to programmatically configure the logger used in the NodeJS SDK. You can now disable logging or add a custom log handler during runtime.

Resource types and traits are an integral part of RAML. We have been working hard in improving our support for them in order to improve your RAML conversion experience on API Transformer. Majority of the improvements target RAML v1.0 while some of them also target v0.8.

OpenAPI/Swagger allows you to include external documentation in your API description for various components. API Transformer now supports conversion of this information for both import/export of OpenAPI/Swagger files.

We’ve updated the version for jackson-databind, a dependency of our Java SDK, due to a vulnerability found in the previous version of the library. We recommend that you generate and redeploy your Java SDK to get the fix.

We’re releasing a new version of our Developer Experience Portal which improves docs generation for all SDKs. This is a breaking change and requires manual migration. Check out all the changes below.

We have added information about the minimum required Java version to the pom.xml file in Java projects. The enforced version has not changed and is still Java 7. Previously if the user tried to use our Java SDK with a lower version, they would face compilation failure and receive error messages that were sometimes ambiguous. Now a Maven build failure is caused which clearly informs the user that the problem is with the version of Java being used. To benefit from this change, please generate your Java SDKs again.