Boost Your Performance and Developer Productivity with Jakarta EE 11
summary
Jakarta EE 11 adds Java 21 support while compiling APIs to Java 17, introduces a new Jakarta Data spec (Spring‑Data‑style repositories), formalizes a runtime‑aware virtual=true flag for managed executors so virtual threads are used on Java 21+ but fall back on platform threads, and removes managed beans removed from the mandatory platform (stays standalone). Demos run on Open Liberty with PostgreSQL and show repository save/find and a virtual‑thread demo working on Java 24; platform release is delayed about a year, feature‑complete since May.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:23History of Enterprise Java
- 8:27Jakarta EE 11 overview
- 13:49Jakarta EE 11 release timeline
- 15:58Removed specifications in Jakarta EE 11
- 18:28Security updates in Jakarta EE 11
- 21:38Concurrency and virtual threads
- 29:48CDI and records support
- 30:11Persistence updates in Jakarta EE 11
- 31:35Validation and records support
- 32:20New Jakarta Data specification
- 39:11Spring and Jakarta EE overlap
- 40:34Jakarta EE 12 plans
- 45:07Future of Jakarta EE
- 47:17Migration tools and resources
- 49:20Closing and resources
related talks
44mJakarta EE 11 - Performance and Developer Productivity
46mThe Evolution of Enterprise Java with Jakarta EE 11 and Beyond
32mPrepare for Jakarta EE 11!
43mPrepare for Jakarta EE 11!
48mA Developer's Guide to #JakartaEE 11
44mThe Past, Present, and Future of Enterprise Java
46mJakarta EE 11: Going Beyond the Era of Java EE
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE