Craving to deploy your Cloud Foundry applications on Tomcat 10 runtime and make use of the latest and greatest Jakarta EE technologies? Got an app using Spring Boot and had to upgrade it to version 3.x due to Spring Boot 2.x EoL? Version 2.x of SAP BTP Security Services Integration Libraries is no longer sufficient as your applications require version 3.x?
No more wait and fear! SAP Java Buildpack 2 is here!
NOTE: - This new major version of SAP Java Buildpack co-exists along with its older counterpart - from now on referred to as SAP Java Buildpack 1 (SJB 1).
- For the time being, you can keep using SJB 1, but we highly recommend that you migrate your Java applications to SJB 2 at your earliest convenience. Deprecation plans for SJB 1 will be announced separately.
|
Now, let's take a closer peek at the core features of SAP Java Buildpack 2:
- The first release provides support for Java 17 (via SapMachine JRE 17).
- You can deploy Java applications on Tomcat 10.1.x. It implements Servlet 6.0, JSP 3.1, EL 5.0, WebSocket 2.1, and Authentication 3.0 specifications (the versions required by the Jakarta EE 10 platform).
- You can use version 3.x of SAP BTP Security Services Integration Libraries.
- Our plans are to gradually add support for Java 21 as well as the latest version of the Apache TomEE runtime (adding support for even more Jakarta EE technologies).
NOTE: Effective April 4, SAP Java Buildpack 2 now supports Java 21. See release notes.
To use the new buildpack, refer to it in your manifest.yml or mtad.yml file, like this:
---
applications:
- name: <APP_NAME>
buildpacks:
- sap_java_buildpack_jakarta
...
Or specify it directly in the cf push command, like this:
cf push -f <PATH_TO_APP_MANIFEST> -b sap_java_buildpack_jakarta
To learn more, see the official documentation: SAP Java Buildpack 2
