Feature epic details
Operating systems
Does the documentation apply to all operating systems?
Summary
Provide a concise summary of your feature. What is the update, why does it matter, and to whom? What do 80% of target users need to know to be most easily productive using your runtime update?
Jakarta EE 11 provides the next evolution of the Jakarta EE 11.
Updates to existing topics
Jakarta EE overview page do the following:
Add Java SE 25 to the Java SE evolved through a series of versions as more classes were added to the JCL, new APIs were introduced, and some older functions were deprecated and replaced. Currently, the following versions of Java SE are maintained with long-term support (LTS): section
Add the below bullet to the Java EE, which is now the open source Jakarta EE platform, has also evolved over a series of versions: section
- In June 2025, Jakarta EE 11 was released. This release included many API changes, adds the new Jakarta Data 1.0 specification, and dropped support for Java SE 11.
In the Java SE Compatibility table add:
Jakarta EE 11 with a supported Java SE level of 17+.
In the See also section add a link to the Differences between Jakarta EE 11 and 10 page
Create a new topic
Add platform global differences section to the EE 11 and EE 10 differences page like: Differences between Jakarta EE 10.0 and 9.1 has.
Global differences between Jakarta EE 11 and 10
The following changes apply across the Jakarta EE 11 platform.
Java SE requirement
Jakarta EE 10 Liberty features can run with Java SE versions 11 and later. All Jakarta EE 11 Liberty features require Java 17 or later, as outlined by the Jakarta EE 11 specification.
Managed Beans Removal
Unlike the jakartaee-10.0 Liberty feature, the jakartaee-11.0 Liberty feature no longer enables the managedBeans-2.0 Liberty feature, as the Managed Beans specification was removed from the platform. Similarly, the jakarta.annotation.ManagedBean annotation API was also removed from the Jakarta Annotations API. Applications relying on the @ManagedBean annotation must migrate to use CDI annotations.
New Jakarta Data Specification
The Jakarta Data 1.0 specification was added to the Jakarta EE 11 platform as well as the Web Profile 11.0 specification. This specification adds a repository-based API for interacting with data. Either the data-1.0 or dataContainer-1.0 Liberty feature enables this function. For more information about how to use this new API, see the Jakarta Data documentation. [Put a link to that Open Liberty documentation here]
Optional Specification Availability
The Jakarta EE 11 Platform specification removes all optional specifications from the platform, meaning Jakarta SOAP with Attachments, XML Binding, XML Web Services, and Enterprise Beans 2.x API functions are not included any longer with the jakartaee-11.0 Liberty feature. Similarly, when using the enterpriseBeans-4.0 convenience feature, it will no longer provide the Enterprise Beans 2.x APIs when combined with other Jakarta EE 11 Liberty features. To use these functions, explicitly add Liberty features to your server's feature list: xmlBinding-4.0 for XML Binding, xmlWS-4.0 for SOAP with Attachments and XML Web Services, and enterpriseBeansHome-4.0 for Jakarta Enterprise Beans 2.x APIs. Alternatively, use the equivalent versionless features with the jakartaee-11.0 platform.
When using the Liberty application client with the jakartaeeClient-11.0 Liberty feature, Jakarta SOAP with Attachments, XML Binding, and XML Web Services client functions are not available. To continue using these functions in your Liberty application client, enable the xmlBinding-4.0 and the new xmlWSClient-4.0 Liberty features in your client's feature list.
Java Security Support
Use of a SecurityManager with Liberty to enable Java Security will no longer work when using Jakarta EE 11 features due to the Jakarta EE 11 platform removing Java Security support. The Liberty runtime will automatically disable the SecurityManager if Java security is configured in the server. This is only an issue when using Java SE 17, since Liberty already disables the SecurityManager when using Java SE 18 and later releases.
Add the Jakarta EE 11 javadoc to the openliberty.io/docs reference section like done with the other Jakarta EE releases.
Feature epic details
Operating systems
Does the documentation apply to all operating systems?
Summary
Provide a concise summary of your feature. What is the update, why does it matter, and to whom? What do 80% of target users need to know to be most easily productive using your runtime update?
Jakarta EE 11 provides the next evolution of the Jakarta EE 11.
Updates to existing topics
Jakarta EE overview page do the following:
Add
Java SE 25to theJava SE evolved through a series of versions as more classes were added to the JCL, new APIs were introduced, and some older functions were deprecated and replaced. Currently, the following versions of Java SE are maintained with long-term support (LTS):sectionAdd the below bullet to the
Java EE, which is now the open source Jakarta EE platform, has also evolved over a series of versions:sectionIn the
Java SE Compatibilitytable add:Jakarta EE 11with a supported Java SE level of17+.In the See also section add a link to the
Differences between Jakarta EE 11 and 10pageCreate a new topic
Add platform global differences section to the EE 11 and EE 10 differences page like: Differences between Jakarta EE 10.0 and 9.1 has.
Global differences between Jakarta EE 11 and 10
The following changes apply across the Jakarta EE 11 platform.
Java SE requirement
Jakarta EE 10 Liberty features can run with Java SE versions 11 and later. All Jakarta EE 11 Liberty features require Java 17 or later, as outlined by the Jakarta EE 11 specification.
Managed Beans Removal
Unlike the
jakartaee-10.0Liberty feature, thejakartaee-11.0Liberty feature no longer enables themanagedBeans-2.0Liberty feature, as the Managed Beans specification was removed from the platform. Similarly, thejakarta.annotation.ManagedBeanannotation API was also removed from the Jakarta Annotations API. Applications relying on the@ManagedBeanannotation must migrate to use CDI annotations.New Jakarta Data Specification
The Jakarta Data 1.0 specification was added to the Jakarta EE 11 platform as well as the Web Profile 11.0 specification. This specification adds a repository-based API for interacting with data. Either the
data-1.0ordataContainer-1.0Liberty feature enables this function. For more information about how to use this new API, see the Jakarta Data documentation.[Put a link to that Open Liberty documentation here]Optional Specification Availability
The Jakarta EE 11 Platform specification removes all optional specifications from the platform, meaning Jakarta SOAP with Attachments, XML Binding, XML Web Services, and Enterprise Beans 2.x API functions are not included any longer with the
jakartaee-11.0Liberty feature. Similarly, when using theenterpriseBeans-4.0convenience feature, it will no longer provide the Enterprise Beans 2.x APIs when combined with other Jakarta EE 11 Liberty features. To use these functions, explicitly add Liberty features to your server's feature list:xmlBinding-4.0for XML Binding,xmlWS-4.0for SOAP with Attachments and XML Web Services, andenterpriseBeansHome-4.0for Jakarta Enterprise Beans 2.x APIs. Alternatively, use the equivalent versionless features with thejakartaee-11.0platform.When using the Liberty application client with the
jakartaeeClient-11.0Liberty feature, Jakarta SOAP with Attachments, XML Binding, and XML Web Services client functions are not available. To continue using these functions in your Liberty application client, enable thexmlBinding-4.0and the newxmlWSClient-4.0Liberty features in your client's feature list.Java Security Support
Use of a
SecurityManagerwith Liberty to enable Java Security will no longer work when using Jakarta EE 11 features due to the Jakarta EE 11 platform removing Java Security support. The Liberty runtime will automatically disable theSecurityManagerif Java security is configured in the server. This is only an issue when using Java SE 17, since Liberty already disables theSecurityManagerwhen using Java SE 18 and later releases.Add the Jakarta EE 11 javadoc to the openliberty.io/docs reference section like done with the other Jakarta EE releases.