Jakarta EE 11

Developer Productivity

Jakarta Data

The new Jakarta Data specification simplifies data access and enhances productivity by separating persistence logic across databases from the model using a simple interface. Key features include:

• BasicRepository: A built-in repository supertype for performing basic operations on entities.
• CrudRepository: Facilitates basic CRUD operations, making database interactions more straightforward and less error-prone.
• Pagination: Support for two types of pagination: offset and cursor.
• Jakarta Data Query Language: A streamlined query language designed to specify the semantics of query methods within Jakarta Data repositories.

Streamlining the Platform

• The Removal of Managed Beans: The Managed Beans specification has been deprecated and removed from Jakarta EE 11 and replaced by CDI (Context and Dependency Injection) alternatives.
• The removal of all references to the Java SE SecurityManager: Aligning with JEP 411, all references to SecurityManager have been removed, paving the way for more modern security practices.
• The removal of optional features to lower the barrier for new vendors: All optional specifications have been removed in Jakarta EE 11.
• Embracing Java Records: Continued support for Java Records with various specifications (e.g. Java Validation) to ensure data integrity and reduce boilerplate code

Performance

Java Platform Support: The new release supports Java 17 or higher, with unique enhancements for those using Java 21 or above, such as:

• Virtual Threads: The updated Concurrency specification enables developers to leverage virtual threads in Java 21 to significantly boost performance, allowing more efficient handling of concurrent tasks without the overhead of traditional thread management.

Jakarta EE 11's Key Updates

Key updates include:

• Java SE Records can now be marked as @Embeddable or @IdClass in Jakarta Persistence 3.2.
• Validation rules can be applied to Java SE Records in Jakarta Validation 3.1.
• Jakarta Persistence 3.2 automatically maps java.time.Instant and java.time.Year as built-in types.
• The use of java.util/java.sql, Date/Time/Timestamp/Calendar and @Temporal is deprecated in Persistence 3.2, in favor of the java.time API.
• An EntityManager can now be @Injected with a defined Jakarta Contexts and Dependency Injection (CDI) scope in Persistence 3.2.
• Jakarta Concurrency 3.1 introduces support for Java SE Virtual Threads in managed resources, such as via @ManagedExecutorDefinition.
• Persistence 3.2 enhances query capabilities with various SQL-like features such as concat (||), union, intersect, except, cast, left, right, and replace.
• Persistence units can be configured using Java, providing an alternative to the persistence.xml file in Persistence 3.2.
• Producers can now specify an @Priority using CDI 4.1.
• The @Context annotation has been deprecated in Jakarta RESTful Web Services 4.0.
• Specifications for Jakarta SOAP with Attachments and Jakarta XML Binding have been removed from the Jakarta EE 11 platform.
• The requirement for Common Object Request Broker Architecture (CORBA) interoperability has been eliminated.
• The @jakarta.annotation.ManagedBean annotation is deprecated.
• All specifications in Jakarta EE 11 have removed dependencies on the Java SE SecurityManager.