Last checked and updated on 20 May 2026
What Is New in Jakarta EE Platform 11
Jakarta EE 11 delivers a streamlined platform focused on modern cloud-native development, removing legacy constraints and enhancing core APIs. The update prioritizes alignment with current Java SE versions and introduces key specifications for building robust applications.
| Category | Key Changes |
|---|---|
| New Features | Introduction of Jakarta Data and new Concurrency specifications. |
| API Updates | Major updates to Core Profile, JSON Processing, REST, and Servlet. |
| Removals | Dropped outdated specs: Jakarta Authorization, Security, and SOAP. |
| Java SE Alignment | Requires a minimum of Java SE 17 or later to run. |
What are the major new specifications in Jakarta EE 11?
Jakarta EE 11 introduces two major new APIs designed for modern application patterns. These additions fill critical gaps in the platform's offering for contemporary development.
Jakarta Data
This new specification provides a unified programming model for data repositories, supporting both relational and NoSQL databases. It allows developers to interact with diverse data stores using a consistent approach, simplifying data access layers.
Jakarta Concurrency
Originally part of Jakarta EE 10 but now a full platform requirement, this spec provides standard APIs for managing concurrent tasks. It brings essential concurrency utilities from Java SE into the Jakarta EE environment with container-aware capabilities.
Which core APIs received significant updates?
Several foundational APIs were upgraded to incorporate new features and Java language improvements. These updates ensure the core of Jakarta EE remains modern and efficient.
Jakarta REST
The RESTful Web Services API now includes support for the widely adopted @ApplicationPath annotation directly within the specification. This clarifies the standard way to define the base URI for all REST resources in an application.
Jakarta Servlet
Servlet gets updates for HTTP methods and request/response processing enhancements. These changes provide better alignment with modern HTTP protocol features and improve the developer experience.
Jakarta JSON Processing
The JSON Processing API now supports the latest JSON standards and includes new convenience methods for working with JSON data structures. This makes handling JSON payloads more straightforward in REST services and other components.
What was removed from the platform?
Jakarta EE 11 removes several specifications that were deemed outdated or redundant. This pruning keeps the platform lean and focused on technologies relevant for new projects.
The removed specifications include Jakarta Authorization, Jakarta Security, and Jakarta SOAP. These were often implemented by vendors but are no longer required components. In practice, this means vendors have more flexibility in their implementations, focusing on the most-used APIs.
What are the Java SE requirements for Jakarta EE 11?
Jakarta EE 11 requires Java SE 17 or later as a minimum runtime environment. This alignment with a modern Java LTS version allows applications to use recent language features and performance improvements.
The shift to Java 17 as the baseline means developers can use language features like records, text blocks, and sealed classes in their Jakarta EE applications. This matters because it synchronizes the platform with the current Java ecosystem, making development more productive.
FAQ
Do I have to use Java 17 with Jakarta EE 11?
Yes, Jakarta EE 11 requires Java SE 17 or a later version. You cannot run it on older Java versions like 11 or 8.
What is the main goal of the new Jakarta Data specification?
It provides a unified repository-based model for accessing both relational and NoSQL data stores, simplifying data persistence code.
Can I still use SOAP web services in Jakarta EE 11?
The Jakarta SOAP specification was removed from the required platform list. While vendors might still offer it, it's no longer a core platform requirement.
Is the Core Profile still part of Jakarta EE 11?
Yes, the Core Profile received updates and remains a key part of the platform for building lightweight, minimalistic applications.
How does the removal of Jakarta Security affect my application?
Your application's security is handled by the implementation (like GlassFish or WildFly), which will provide its own security mechanisms that go beyond the old, removed specs.