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.22.0
- Continuous delivery toolkit in version v36
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.22.0
You can update your dependencies of the SAP Cloud SDK for Java to version 3.22.0 and get the new version from Maven Central.
OData Batch Requests (new experimental API)
This version contains an experimental API for issuing generic OData batch requests using
ODataRequestBatch. This implementation supports batching of entity read and modification requests. Modifications are grouped within changesets and, depending on the service implementation, they are expected to rollback if a change in the set was unsuccessful. Multiple changesets and read requests can be attached.
HttpClient httpClient = getHttpClient(); ODataRequestRead read1 = getReadReq(); ODataRequestCreate create2 = getCreateReq(); ODataRequestUpdate update3 = getUpdateReq(); ODataRequestBatch batchRequest = new ODataRequestBatch( "service-path/", ODataProtocol.V4 ) .addRead( read1 ) .beginChangeset() .addCreate( create2 ) .addUpdate( update3 ) .endChangeset(); batchRequest.execute( httpClient );
Please note that the API is not considered final yet.
Several further improvements are listed in the full release notes.
Among several bugfixes, we resolved an issue with missing validation of URL used for obtaining the JWT verification key.
As usual, the full release notes contain a list of all improvements in this release.
Continuous Delivery Toolkit: Release Highlights v36
We have also released version v36 of our out-of-the-box continuous delivery offering consisting of a ready-made Jenkins server and a complete delivery toolkit.
Although this is a maintenance release, it contains some improvements under the hood.
You can find all fixes and improvements in the complete release notes.
How to Update
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
- Update the version of that dependency to
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.22.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-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.22.0.
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
Continuous Delivery Toolkit
If you are using the pipeline with a fixed version (as recommended since v7), update the continuous delivery toolkit with the following command, that you run on the server hosting the cx-server:
./cx-server update image
Learn more about SAP Cloud SDK
To learn how others in the community use SAP Cloud SDK you can check out more related blog posts.
Are you interested in a particular topic? It might be helpful to search the Q&A place? Feel free to ask your question there and do not forget to select the tag
SAP Cloud SDK.
If you are new to SAP Cloud SDK, get started and gain first hand-on exercise by following our tutorials.