Get Ready for Jakarta EE 10!

Is enterprise Java ready for native compilation? Jakarta EE 10's new Core Profile and build-time CDI make it a reality for modern microservices.

#1about 2 minutes

Understanding Jakarta EE specifications and artifacts

Jakarta EE specifications are defined by a document, an API artifact, a Test Compatibility Kit (TCK), and at least one compatible open-source implementation.

#2about 2 minutes

Exploring the new profiles and updates in Jakarta EE 10

Jakarta EE 10 introduces major updates to most specifications, adds concurrency to the Web Profile, and introduces the new Core Profile for microservices.

#3about 1 minute

Understanding Java SE 11 and 17 compatibility

Jakarta EE 10 APIs are compiled for Java SE 11, but the TCK is tested against both Java SE 11 and 17, allowing developers to use newer Java features.

#4about 3 minutes

New features in Jakarta Security and Persistence

Jakarta Security 3.0 adds standardized OpenID Connect support, while Jakarta Persistence 3.1 introduces native support for UUID as a basic type.

#5about 5 minutes

Bootstrapping a REST application without an application server

The new Java SE Bootstrap API in Jakarta REST allows you to run a RESTful application as a standalone runnable JAR file without a full application server.

#6about 3 minutes

Introducing the Jakarta EE Core Profile and CDI Lite

The new Core Profile targets smaller runtimes like Helidon and Quarkus, using CDI Lite with build-compatible extensions to enable native compilation via GraalVM.

#7about 7 minutes

Migrating an application from Jakarta EE 8 to 9

Learn the key steps for migrating from the `javax` to the `jakarta` namespace, including updating dependencies, fixing imports, and changing XML schema definitions.

#8about 5 minutes

Using Java 17 records with Jakarta EE 9 and 10

Discover how to use Java 17 records for DTOs and see how Jakarta EE 10 improves JSON binding support for records compared to the workarounds needed in version 9.

#9about 4 minutes