Key Updates in Jakarta EE 11

Jakarta EE 11 introduces a number of important specification updates:

Java SE records can now be annotated with @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 legacy java.util / java.sql Date/Time/Timestamp/Calendar types and the @Temporal annotation are deprecated in favor of the java.time API.

EntityManager can now be injected using defined Jakarta Contexts and Dependency Injection (CDI) scopes.

Jakarta Concurrency 3.1 adds support for Java SE virtual threads, usable in managed resources via @ManagedExecutorDefinition.

Persistence 3.2 enhances query capabilities with SQL‑like features such as concat (||), union, intersect, except, cast, left, right, and replace.

Persistence units can now be configured with Java code, providing an alternative to the persistence.xml file.

Producers can specify @Priority using CDI 4.1.

The @Context annotation is deprecated in Jakarta RESTful Web Services 4.0.

Jakarta SOAP with Attachments and Jakarta XML Binding specifications have been removed from the Jakarta EE 11 platform.

Support for the CORBA interoperability architecture has been dropped.

The @jakarta.annotation.ManagedBean annotation is deprecated.

All specifications in Jakarta EE 11 have removed the dependency on the Java SE SecurityManager.

More details at https://jakarta.ee/release/11/