Skip to Content
Product Information

New Version 1.16.0 of SAP Cloud SDK for JavaScript

The issues with the upload of the SAP Cloud SDK for Java to Maven Central have been resolved. The new versions 3.12.0 and 2.27.0 described below are now available.


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

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.12.0

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

Updates on the SAP Blockchain Module

The SAP Blockchain module now allows the usage of custom HTTP clients. We added support for a custom HTTP request factory for the rest template in MultichainRequest.

When creating a MultichainService instance using a SAP Cloud Platform destination, the destination’s HTTP client will now be used as a pre-configured HttpClient instance with authentication, HTTP connection pooling, etc. for each MultichainRequest.

Further improvements

In this version we resolved an issue with the OData generator for cases where .edmx files declared EntitySets with related service operations annotations. Operations on EntitySets with no annotations set were wrongly ignored in the generation process. In the fixed version all operations for EntitySets without annotations are considered in the generation process.

Several further improvements are listed in the full release notes.

Java Libraries: Release Highlights 2.27.0

We have also released the SDK for Java in a new maintenance version 2.27.0. Everyone who did not yet upgrade 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.16.0

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

Support for filter functions

In the new version we introduced support for using the following OData V2 filter functions in OData queries:

For filtering with those functions use:

SomeEntity.requestBuilder()
    .getAll()
    .filter(length(SomeEntity.FIELD).greaterThan(10));

In addition to supporting those predefined filter functions, we added support for representing other OData functions to be used in filtering. Use the filterFunction factory function to filter by using any of the OData v2 filter functions generically. For example, to represent the concat function in filters, use:

...filter(
    filterFunction('concat', 'string', 'prefix', SomeEntity.FIELD)
      .equals('prefixSomeName')
);

Of course, you can also put that into your own function definition to reuse it and make the code clearer:

function concat(part1, part2) {
    return filterFunction('concat', 'string', part1, part2);
}
// ...
concat('prefix', SomeEntity.FIELD)
  .equals('prefixSomeName')
// ...

Based on demand, we may add further predefined filter functions to the SAP Cloud SDK in the future.

Further improvements

We have for now disabled the handling of proxy environment variables as the underlying Axios library has an issue that leads to failing requests once a proxy is defined. Now, at least requests that do not rely on the proxy will work.

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.12.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.12.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.12.0.

Of course, you can also generate a new project that uses version 3.12.0 from the start by running the Maven archetypes for Neo or Cloud Foundry with -DarchetypeVersion=3.12.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.

/
Be the first to leave a comment
You must be Logged on to comment or reply to a post.