The 11th release of Jakarta EE, the open-source successor to Java EE whose advancement is led by the Eclipse Foundation, is still undergoing development. Scheduled for release later in 2024, Jakarta EE 11 will introduce a range of enhancements and new functionalities aimed at improving Java enterprise application development. Let’s take a quick look at what to expect.
Java SE Alignment
Jakarta EE 11 will be based on Java SE 17/21, a, incorporating the latest advancements in the Java ecosystem. This update will include support for Records and Virtual Threads, as well as adaptations to address the deprecation of the Security Manager. These alignments will help ensure Jakarta EE remains modern and can leverage the latest Java SE innovations.
CDI Alignment and Enhancements for Jakarta EE 11
Continuing the trend from previous versions, Jakarta EE 11 further aligns various specifications with Jakarta Contexts and Dependency Injection (CDI). This includes improved CDI support in Jakarta REST, Jakarta Persistence and Jakarta Concurrency APIs. You can expect more consistent and intuitive programming models across the different Jakarta EE technologies.
Specification Updates
Several core Jakarta EE specifications are receiving significant updates:
Jakarta Persistence
- Support for Java SE Records as embeddable classes
- Enhanced date/time handling with Instant and Year support
- More SQL-like features in JPQL and Criteria API
- Thread-safe EntityManager injection
- Optional persistence.xml configuration
Jakarta Concurrency
- Adapting to Virtual Threads
- New annotations like @Schedule and @MaxConcurrency for CDI beans
- Support for the Flow API
Jakarta Security
- JWT alignment
- Support for multiple authentication mechanisms
- In-memory identity store
Jakarta Messaging
- CDI-based @MessageListener
- Jakarta Messaging Lite for cloud-native use cases
- Standalone bootstrap API
New Specifications for Jakarta EE 11
Jakarta EE 11 introduces
- Jakarta Data: A higher-level data access abstraction using the Repository pattern, supporting both JPA and NoSQL databases.
- Jakarta NoSQL (Standalone*): Specification for accessing NoSQL databases with a familiar JPA-like API.
Jakarta NoSQL aims to become a core part of the Jakarta EE Platform as the standard, vendor agnostic API for accessing different NoSQL databases. Unfortunately, it’ll not be a part of the umbrella specification for Jakarta EE 11. However, the project team is working on getting it ready for the next major iteration release. You can however, use it in your Jakarta EE 11 projects by explicitly adding it as dependency.
Deprecations and Removals
As Jakarta EE evolves, some older technologies are being phased out:
- JAX-WS (SOAP)
- JAXB (XML)
- CORBA
- @ManagedBean annotation
- Certain EJB features
Other Notable Changes in Jakarta EE 11
- Java SE Records support in Jakarta Validation, CDI, and Expression Language (EL)
- Removal of Java SE SecurityManager dependency
- @Priority support on producers in CDI
- Deprecation of @Context in favor of CDI injection in Jakarta REST
- Java-based job definition API in Jakarta Batch
Community Focus
Jakarta EE 11 reflects the community-driven nature of the platform. With Eclipse Foundation driving open governance and collaboration, the release incorporates feedback and contributions from various stakeholders in the Java ecosystem.
Summary
Jakarta EE 11 is a major advancement in enterprise Java development. It aims to address the changing requirements of developers in both cloud-native and traditional enterprise settings by adopting new Java features, improving current APIs and introducing fresh specifications. As the release date nears, developers are advised to examine these modifications and think about how they can use them effectively in their applications.
Stay tuned for more updates from Payara on Jakarta EE 11. Consider getting involved in the Jakarta EE community by joining the mailing list to shape the future of this vital technology stack.
3 minutes
