New Versions of SAP Cloud SDK: 3.9.0 for Java and 1.14.0 for JavaScript

[HenningH]

We have released new versions of the SAP Cloud SDK. In detail, the following components are now available in new versions:

• Java libraries in version 3.9.0


• Java libraries in version 2.24.0


• JavaScript libraries in version 1.14.0

In this blog post, we will walk you through the highlights of these releases. For a complete overview, visit our release notes for the Java libraries, for the JavaScript libraries, and for the continuous delivery toolkit. The release notes also include the change log of all our releases so far.
At the end of the article, you will find a set of instructions on how to update to the new versions.

Java Libraries: Release Highlights 3.9.0

You can update your dependencies of the SAP Cloud SDK for Java to version 3.9.0 and consume the new version from Maven Central.

The module for interacting with the blockchain service on SAP Cloud Platform has added support for basic authentication to MultichainRequest, allowing the request to be used with AWS and Azure Multichain nodes. Therefore, the return type of MultichainService.getDestination() changes to MultichainBasicAuthDestination to support Basic Authentication. If you use this method, please adapt to the new return type.

Version 3.9.0 adds a new method DestinationProperties.getPropertyNames() that returns a list with the names of all properties defined on a destination. This allows you to enumerate the names of all properties retrieved from the destination service and, via the corresponding getter, their values.

To make it easier to identify threads spawned by the resilience framework of the SAP Cloud SDK, threads spawned by asynchronous calls now use the new name format cloudsdk-resilience-<number>.

We have updated several dependencies, including those to Jackson from version 2.10.0 to 2.10.1 which fixes the vulnerabilities CVE-2019-17267 and CVE-2019-17531. The dependency to SAP Cloud Application Programming Model Java libraries has been increased from version 1.33.0 to 1.35.2.

We have fixed an issue where special characters such as a forward slash / as part of keys were incorrectly escaped in certain OData requests. This concerned requests made when dynamically fetching a navigation property, for example, with BusinessPartner.fetchBusinessPartnerAddress, of an entity whose key contains such characters.

Version 3.9.0 fixes an issue that caused the OData VDM generator to wrongly identify which operations are available on a service entity in cases where OData annotations where present, but not used for this purpose.

Several further improvements are listed in the full release notes.

Java Libraries: Release Highlights 2.24.0

We have also released the SDK for Java in a new maintenance version 2.24.0. Everyone who did not yet migrate to version 3 of the SDK for Java can consume that version from Maven Central.

For a complete view on what has changed, take a look at the full release notes.

JavaScript Libraries: Release Highlights 1.14.0

The JavaScript libraries of the SAP Cloud SDK are now available in version 1.14.0.

The OData client generator now supports nested complex types in properties of entities for which it generates a JavaScript representation.

In a previous release, we have improved the logging within the SAP Cloud SDK for JavaScript. Version 1.14.0 makes it even easier to configure logging, as it allows setting the log levels of SDK loggers more conveniently through a single function setLogLevel():

import { setLogLevel } from '@sap/cloud-sdk-util';

setLogLevel('debug', 'destination-accessor');

The OData client now allows setting empty string and other falsy values for non-nullable properties as this is supported by SAP S/4HANA Cloud.

As usual, the full release notes contain a list of all improvements in this release.

How to Update

Java libraries

To update the version of the SAP Cloud SDK Java libraries used in an existing project, proceed as follows:

• Open the pom.xml file in the root folder of your project.


• Locate the dependency management section and therein the sdk-bom dependency.


• Update the version of that dependency to 3.9.0.

With this, you are already done thanks to the "bill of material" (BOM) approach. Your dependency should look like this:

<dependencyManagement>

    <dependencies>

        <dependency>

            <groupId>com.sap.cloud.sdk</groupId>

            <artifactId>sdk-bom</artifactId>

            <version>3.9.0</version>

            <type>pom</type>

            <scope>import</scope>

        </dependency>

    </dependencies>

    <!-- possibly further managed dependencies ... -->

</dependencyManagement>

If you update from a version prior to 3.0.0, have a look at our migration guide.

If you are using the SAP Cloud SDK in a project of the SAP Cloud Application Programming Model, replace sdk-bom with sdk-modules-bom to only update the version of SDK modules, not further dependencies.
You can now recompile your project (be aware of the compatibility notes, though) and leverage the new features of the SAP Cloud SDK in version 3.9.0.

Of course, you can also generate a new project that uses version 3.9.0 from the start by running the Maven archetypes for Neo or Cloud Foundry with -DarchetypeVersion=3.9.0 (or RELEASE).

JavaScript libraries

To update the version of the SAP Cloud SDK JavaScript libraries used in an existing project, use the command npm update in the root folder of your module. Note that this will also update other modules, unless you explicitly specify which packages to update. If you want to check beforehand what will change, use npm outdated.