The Eclipse Foundation has announced the release of Jakarta EE 11 Platform, which builds on previous Core Profile (December 2024) and Web Profile (March 2025) versions.
This release signifies advancement in simplifying enterprise Java, emphasising developer productivity and overall performance. Key highlights include modernised Test Compatibility Kits (TCKs), the introduction of the new Jakarta Data specification, major updates to existing specifications, and support for the latest Java LTS release, enabling developers to leverage the enhancements in Java 21, including Virtual Threads.
Key Features of Jakarta EE 11
Since the release of Jakarta EE 10, the enterprise Java renaissance has kept accelerating. Jakarta EE 11 builds on this progress, enhancing performance and increasing developer productivity, led by the introduction of the Jakarta Data specification.
Jakarta Data is a major step forward in simplifying persistence logic within enterprise applications. Key features include:
- BasicRepository: A foundational repository interface that provides out-of-the-box support for essential data operations, reducing boilerplate and setup time.
- CrudRepository: Builds on BasicRepository to offer full Create, Read, Update, and Delete (CRUD) functionality, enabling clean and intuitive database interactions.
- Pagination: Includes support for both offset-based and cursor-based pagination, giving developers flexible tools to efficiently manage large data sets.
- Query Language: Introduces a concise, purpose-built query language that simplifies method-level query definitions directly within Jakarta Data repositories.
These capabilities make Jakarta Data a valuable addition for teams looking to build robust, data-centric applications with less code and greater clarity.
Modernising the TCK
A major part of the release was the modernisation and enhancement of the Jakarta EE Platform Test Compatibility Kit (TCK). This initiative improves maintainability and flexibility by incorporating modern testing tools like JUnit 5 and Maven, making it easier to evolve the TCK alongside the platform. These updates streamline compatibility testing and lower the barrier to contributing new tests, helping to drive future innovation across the Jakarta EE ecosystem. As a result, contributors can get started more easily, and new vendors or developers interested in participating will find it significantly more accessible to join and contribute. Those interested in getting involved can learn more and engage through the Jakarta EE TCK project page.
Streamlining Specifications
Jakarta EE 11 continues its evolution toward a more modern and efficient development model by refining and simplifying its specification set. A notable change is the removal of the deprecated Managed Beans specification, which had long been superseded by more flexible and powerful alternatives. This cleanup helps reduce legacy complexity and clarifies the recommended programming model going forward.
In line with this, the platform places a strong emphasis on Contexts and Dependency Injection (CDI) as the central programming model. CDI has been further enhanced in Jakarta EE 11, now serving as the standard replacement for Managed Beans, promoting consistency and a more declarative development style throughout the ecosystem.
The release also reinforces its commitment to modern Java features by embracing Java Records across various specifications, such as Jakarta Bean Validation. This allows developers to leverage concise, immutable data carriers while still benefiting from validation and integration features, helping to reduce boilerplate and improve readability.
Finally, Jakarta EE 11 aligns with the direction of the Java platform by removing all references to the Java SE SecurityManager, following the deprecation outlined in JEP 411. This shift enables the adoption of more contemporary, fine-grained security mechanisms that better suit today’s cloud-native and modular application architectures.
Leveraging Java 21 Enhancements
Jakarta EE 11 supports Java 17 or higher, with unique enhancements for Java 21 users. One of the most notable features is the updated Concurrency specification, which enables developers to leverage Virtual Threads in Java 21. This results in significant performance gains by allowing efficient handling of concurrent tasks without the overhead of traditional thread management.
Coming Next
Development on Jakarta EE 12 is already in progress, with a planned release in 2026. This next version aims to elevate the platform’s API source level to Java SE 21, while targeting Java SE 25 for runtime support. The community is actively working on enhancements across many specifications, including possible introductions like Jakarta Query and Jakarta MVC, and continued evolution of Jakarta NoSQL. Staying committed to its established two-year release cycle, Jakarta EE continues to prioritize long-term planning and sustained innovation.
Growing Ecosystem and Community Participation
The Jakarta EE ecosystem continues to expand, with many working group members, including Fujitsu, IBM, Oracle, Payara, and Tomitribe, certifying Jakarta EE 11 compatible products. The list of compatible implementations and products is expected to grow rapidly post-release.
The Jakarta EE community actively welcomes contributions and participation from all interested parties. To connect with the global community and participate in ongoing discussions and development efforts, visit the Jakarta EE website.
Anyone interested in contributing or staying informed is encouraged to connect with the community through jakarta.ee/connect/.
