Contributors Guide to the Jakarta EE 11 Galaxy
summary
Jakarta EE 11 targets H1 2024 with Java 21 as the baseline and a firm plan to add Jakarta Data repositories so CRUD interfaces get generated instead of handwritten, plus JWT alignment with MicroProfile and tighter Jakarta Security support for annotations like RolesAllowed. Concurrency gains managed virtual threads via managed executors (virtual=true), EJB annotations such as @Lock and @Schedule move into CDI, records become embeddables in JPA, JAX‑WS/JAXB/CORBA deprecations land, and contribution requires signing the Eclipse Contributor Agreement.
AI-written summary · about
chapters (6)
- 0:00Introduction to Jakarta EE 11
- 10:34Why Jakarta EE matters
- 26:10Jakarta Concurrency updates
- 35:40Jakarta Data and new specs
- 42:23How to contribute to Jakarta EE
- 44:09Summary and call to action
related talks
44mJakarta EE 11 - Performance and Developer Productivity
32mPrepare for Jakarta EE 11!
48mA Developer's Guide to #JakartaEE 11
43mPrepare for Jakarta EE 11!
50mBoost Your Performance and Developer Productivity with Jakarta EE 11
51mJakarta EE 10 and Beyond
48mJakarta EE 10 Feature by Feature
46mThe Evolution of Enterprise Java with Jakarta EE 11 and Beyond