Jakarta EE New Features: What Changed in Version 11
Jakarta EE new features in version 11 represent the most significant evolution of enterprise Java since the transition from Java EE to Eclipse Foundation governance. Therefore, understanding these changes is essential for teams maintaining enterprise applications. As a result, this guide covers the key improvements alongside practical migration strategies.
CDI Lite and Simplified Dependency Injection
CDI Lite provides a trimmed-down dependency injection model optimized for cloud-native deployments. Moreover, it removes rarely-used features like decorators and conversation scope to reduce runtime overhead. Consequently, applications using CDI Lite start faster and consume less memory in containerized environments.
The simplified model retains core injection capabilities including qualifiers, producers, and interceptors. Furthermore, build-time annotation processing replaces much of the runtime reflection, enabling ahead-of-time compilation with GraalVM native images.
Jakarta EE New Features in REST and Data
Jakarta REST 4.0 introduces Server-Sent Events support and improved async processing. Additionally, the entity filtering API allows field-level control over JSON serialization without custom DTOs. For example, you can now annotate entity fields to include or exclude them based on security roles.
// Jakarta REST 4.0 — Server-Sent Events
@Path("/events")
public class EventResource {
@GET
@Produces(MediaType.SERVER_SENT_EVENTS)
public void streamEvents(@Context SseEventSink sink, @Context Sse sse) {
CompletableFuture.runAsync(() -> {
try {
for (int i = 0; i < 10; i++) {
sink.send(sse.newEventBuilder()
.name("update")
.data(String.class, "Event " + i)
.build());
Thread.sleep(1000);
}
} finally {
sink.close();
}
});
}
}
// Jakarta Data 1.0 — Repository pattern
@Repository
public interface ProductRepository extends CrudRepository<Product, UUID> {
@Find
List<Product> findByCategory(@By("category") String cat);
@Query("SELECT p FROM Product p WHERE p.price < :max ORDER BY p.name")
Page<Product> findAffordable(@Param("max") BigDecimal max, PageRequest page);
}Jakarta Data 1.0 standardizes the repository pattern across persistence providers. Therefore, switching between JPA, NoSQL, and other backends requires only configuration changes.
Security and Configuration Updates
Jakarta Security 4.0 adds OpenID Connect client support directly into the specification. However, this previously required vendor-specific extensions or external libraries. In contrast to earlier versions, the standardized OIDC client simplifies multi-provider authentication in enterprise applications.
Jakarta Config introduces externalized configuration with type-safe injection, similar to MicroProfile Config but as a full Jakarta EE specification. Specifically, configuration sources follow a priority chain from environment variables through property files to programmatic defaults.
Migration Path from Jakarta EE 10
Most Jakarta EE 10 applications require minimal changes for version 11 adoption. Additionally, the specification maintains backward compatibility for core APIs while deprecating features targeted for removal in future versions. For instance, applications using standard CDI should add the CDI Lite qualifier to opt into the streamlined model.
Related Reading:
Further Resources:
In conclusion, Jakarta EE new features deliver meaningful improvements for cloud-native enterprise Java while maintaining backward compatibility. Therefore, plan your migration to benefit from CDI Lite, Jakarta Data, and standardized security capabilities.