26.0.0.5 post#4816
Closed
navaneethsnair1 wants to merge 3 commits into
Closed
Conversation
| author_picture: https://avatars3.githubusercontent.com/navaneethsnair1 | ||
| author_github: https://github.com/navaneethsnair1 | ||
| seo-title: Jakarta EE 11, SpringBoot 4.0, and more in 26.0.0.5- OpenLiberty.io | ||
| seo-description: This release adds support for Jakarta EE 11 and Spring Boot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying Spring Boot 4.x applications in both JAR and WAR formats. |
Contributor
There was a problem hiding this comment.
Suggested change
| seo-description: This release adds support for Jakarta EE 11 and Spring Boot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying Spring Boot 4.x applications in both JAR and WAR formats. | |
| seo-description: This release adds support for Jakarta EE 11 and SpringBoot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying SpringBoot 4.x applications in both JAR and WAR formats. |
| author_github: https://github.com/navaneethsnair1 | ||
| seo-title: Jakarta EE 11, SpringBoot 4.0, and more in 26.0.0.5- OpenLiberty.io | ||
| seo-description: This release adds support for Jakarta EE 11 and Spring Boot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying Spring Boot 4.x applications in both JAR and WAR formats. | ||
| blog_description: This release adds support for Jakarta EE 11 and Spring Boot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying Spring Boot 4.x applications in both JAR and WAR formats. |
Contributor
There was a problem hiding this comment.
Suggested change
| blog_description: This release adds support for Jakarta EE 11 and Spring Boot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying Spring Boot 4.x applications in both JAR and WAR formats. | |
| blog_description: This release adds support for Jakarta EE 11 and SpringBoot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying SpringBoot 4.x applications in both JAR and WAR formats. |
| // change the "IMAGE CAPTION" to a couple words of what the image is | ||
| // // // // // // // // | ||
|
|
||
| This release adds support for Jakarta EE 11 and Spring Boot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying Spring Boot 4.x applications in both JAR and WAR formats. |
Contributor
There was a problem hiding this comment.
Suggested change
| This release adds support for Jakarta EE 11 and Spring Boot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying Spring Boot 4.x applications in both JAR and WAR formats. | |
| This release adds support for Jakarta EE 11 and SpringBoot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying SpringBoot 4.x applications in both JAR and WAR formats. |
|
|
||
| Jakarta EE 11 Core Profile, Web Profile and Platform are now officially supported in Open Liberty! We’d like to start by thanking all those who provided feedback throughout our various betas. | ||
|
|
||
| Jakarta EE 11 marks a major milestone. It is the first Jakarta release to add a new specification to the platform since Java EE 8 in 2017 and, therefore, the first to provide a new component specification since the platform was taken over by the Eclipse Foundation. Among the many updates to existing spJavaecifications, it also removes all optional specifications and functions from the Platform. Liberty continues to support those optional specifications and functions when combined with Jakarta EE 11 features. |
Contributor
There was a problem hiding this comment.
Suggested change
| Jakarta EE 11 marks a major milestone. It is the first Jakarta release to add a new specification to the platform since Java EE 8 in 2017 and, therefore, the first to provide a new component specification since the platform was taken over by the Eclipse Foundation. Among the many updates to existing spJavaecifications, it also removes all optional specifications and functions from the Platform. Liberty continues to support those optional specifications and functions when combined with Jakarta EE 11 features. | |
| Jakarta EE 11 marks a major milestone. It is the first Jakarta release to add a new specification to the platform since Java EE 8 in 2017 and, therefore, the first to provide a new component specification since the platform was taken over by the Eclipse Foundation. Among the many updates to existing Java specifications, it also removes all optional specifications and functions from the Platform. Liberty continues to support those optional specifications and functions when combined with Jakarta EE 11 features. |
|
|
||
| Jakarta EE 11 marks a major milestone. It is the first Jakarta release to add a new specification to the platform since Java EE 8 in 2017 and, therefore, the first to provide a new component specification since the platform was taken over by the Eclipse Foundation. Among the many updates to existing spJavaecifications, it also removes all optional specifications and functions from the Platform. Liberty continues to support those optional specifications and functions when combined with Jakarta EE 11 features. | ||
|
|
||
| The Core Profile specification was introduced in Jakarta EE 10 to provide a profile for lightweight cloud native applications such as MicroProfile-based applications. With the introduction of Jakarta EE 11 support in this release, the MicroProfile 7.0 and 7.1 features also now work with Jakarta EE 11 so that you can run your MicroProfile 7 applications using either Jakarta EE 10 or Jakarta EE 11 features. |
Contributor
There was a problem hiding this comment.
Suggested change
| The Core Profile specification was introduced in Jakarta EE 10 to provide a profile for lightweight cloud native applications such as MicroProfile-based applications. With the introduction of Jakarta EE 11 support in this release, the MicroProfile 7.0 and 7.1 features also now work with Jakarta EE 11 so that you can run your MicroProfile 7 applications using either Jakarta EE 10 or Jakarta EE 11 features. | |
| The Core Profile specification was introduced in Jakarta EE 10 to provide a profile for lightweight cloud-native applications such as MicroProfile-based applications. With the introduction of Jakarta EE 11 support in this release, the MicroProfile 7.0 and 7.1 features now also work with Jakarta EE 11. You can run your MicroProfile 7 applications using either Jakarta EE 10 or Jakarta EE 11 features. |
| | link:https://jakarta.ee/specifications/messaging/3.1/[Messaging 3.1] |Unchanged | link:https://openliberty.io/docs/latest/reference/feature/messaging-3.1.html[messaging-3.1] | ||
| |=== | ||
|
|
||
| * Enterprise Beans 4.0 is unchanged, but the optional EJB 2.x function is no longer enabled when the `enterpriseBeans-4.0` feature is configured with other Jakarta EE 11 features and now requires the user to also add `enterpriseBeansHome-4.0` feature if they want to use EJB 2.x APIs. |
Contributor
There was a problem hiding this comment.
Suggested change
| * Enterprise Beans 4.0 is unchanged, but the optional EJB 2.x function is no longer enabled when the `enterpriseBeans-4.0` feature is configured with other Jakarta EE 11 features and now requires the user to also add `enterpriseBeansHome-4.0` feature if they want to use EJB 2.x APIs. | |
| * Enterprise Beans 4.0 is unchanged, but the optional EJB 2.x function is no longer enabled when the `enterpriseBeans-4.0` feature is configured with other Jakarta EE 11 features. Users who want to use EJB 2.x APIs must also add the `enterpriseBeansHome-4.0` feature. |
| // // // // // // // // | ||
| [#springboot] | ||
| == SpringBoot 4.0 | ||
| Open Liberty currently supports running Spring Boot 1.5, 2.x, and 3.x applications. With the introduction of the new `springBoot-4.0` feature, users can now deploy Spring Boot 4.x applications by enabling this feature. While Liberty consistently supports Spring Boot applications packaged as `WAR` files, this enhancement extends support to both `JAR` and `WAR` formats for Spring Boot 4.x applications. |
Contributor
There was a problem hiding this comment.
Suggested change
| Open Liberty currently supports running Spring Boot 1.5, 2.x, and 3.x applications. With the introduction of the new `springBoot-4.0` feature, users can now deploy Spring Boot 4.x applications by enabling this feature. While Liberty consistently supports Spring Boot applications packaged as `WAR` files, this enhancement extends support to both `JAR` and `WAR` formats for Spring Boot 4.x applications. | |
| Open Liberty currently supports running Spring Boot 1.5, 2.x, and 3.x applications. With the introduction of the new `springBoot-4.0` feature, users can now deploy Spring Boot 4.x applications. While Liberty has consistently supported Spring Boot applications packaged as `WAR` files, this enhancement extends support to both `JAR` and `WAR` formats for Spring Boot 4.x applications. |
| == SpringBoot 4.0 | ||
| Open Liberty currently supports running Spring Boot 1.5, 2.x, and 3.x applications. With the introduction of the new `springBoot-4.0` feature, users can now deploy Spring Boot 4.x applications by enabling this feature. While Liberty consistently supports Spring Boot applications packaged as `WAR` files, this enhancement extends support to both `JAR` and `WAR` formats for Spring Boot 4.x applications. | ||
|
|
||
| The `springBoot-4.0` feature provides complete support for running a Sprint Boot 4.x application on Open Liberty as well as having the capability to thin the application when creating applications in containers. |
Contributor
There was a problem hiding this comment.
Suggested change
| The `springBoot-4.0` feature provides complete support for running a Sprint Boot 4.x application on Open Liberty as well as having the capability to thin the application when creating applications in containers. | |
| The `springBoot-4.0` feature provides complete support for running a Spring Boot 4.x application on Open Liberty, as well as the ability to thin the application when building containerized applications. |
|
|
||
| The `springBoot-4.0` feature provides complete support for running a Sprint Boot 4.x application on Open Liberty as well as having the capability to thin the application when creating applications in containers. | ||
|
|
||
| To use this feature, the user must be running `Java 17` or later with EE11 features enabled. If the application uses servlets, it must be configured to use `Servlet 6.1`. Include the following features in your `server.xml` file to define the settings. |
Contributor
There was a problem hiding this comment.
Suggested change
| To use this feature, the user must be running `Java 17` or later with EE11 features enabled. If the application uses servlets, it must be configured to use `Servlet 6.1`. Include the following features in your `server.xml` file to define the settings. | |
| To use this feature, users must be running `Java 17` or later with Jakarta EE 11 features enabled. If the application uses servlets, it must be configured to use `Servlet 6.1`. Include the following features in your `server.xml` file to configure the server. |
| </features> | ||
| ---- | ||
|
|
||
| The `server.xml` configuration for deploying a Spring Boot application follows the same approach as in earlier Liberty Spring Boot versions. |
Contributor
There was a problem hiding this comment.
Suggested change
| The `server.xml` configuration for deploying a Spring Boot application follows the same approach as in earlier Liberty Spring Boot versions. | |
| The `server.xml` configuration for deploying a Spring Boot application follows the same approach used in earlier Liberty Spring Boot versions. |
| <springBootApplication id="spring-boot-app" location="spring-boot-app-0.1.0.jar" name="spring-boot-app" /> | ||
| ---- | ||
|
|
||
| As in earlier versions, the Spring Boot application JAR can be deployed by placing it in the `/dropins/spring` folder. The `springBootApplication` configuration in the `server.xml` file can be omitted when using this deployment method. |
Contributor
There was a problem hiding this comment.
Suggested change
| As in earlier versions, the Spring Boot application JAR can be deployed by placing it in the `/dropins/spring` folder. The `springBootApplication` configuration in the `server.xml` file can be omitted when using this deployment method. | |
| As in earlier versions, the Spring Boot application JAR can be deployed by placing it in the `/dropins/spring` folder. The `springBootApplication` configuration in the `server.xml` file can be omitted when this deployment method is used. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://github.com/OpenLiberty/blogs/blob/26.0.0.5-post/posts/2026-05-19-26.0.0.5.adoc