"Jakarta EE 11 and Beyond"
summary
Jakarta EE 11 arrives with a Java 17 baseline, support for records and virtual threads, removal of the security manager, and a new Jakarta Data spec that auto-generates repositories for SQL and NoSQL. Persistence 3.2 adds embeddable records, programmatic persistence config, and thread‑safe EntityManager injection; the TCK moves from Ant to Maven. Adoption stats cited: ~25–35% of apps run in an EE container and ~70–80% use at least one Jakarta API.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:50Jakarta EE evolution
- 4:42Jakarta EE impact
- 6:46Jakarta EE 10 overview
- 8:09Ambassadors role
- 8:52Jakarta EE 10 features
- 10:55Jakarta EE 11 changes
- 13:03Jakarta Persistence 3.2
- 15:52Jakarta Persistence demo
- 16:13Jakarta Validation & Concurrency
- 17:13Jakarta EE 12 proposals
- 18:59Jakarta Security & Data
- 20:47Jakarta Data explained
- 21:54Jakarta EE 12 features
- 24:19Jakarta NoSQL & Config
- 25:47Contributing to Jakarta EE
- 26:52Getting started resources
- 27:55AI tools for Jakarta EE
- 28:15Summary & call to action
related talks
35mMicroProfile and Jakarta EE -- What's Next?
55m10 strategies for developing reliable Jakarta EE & MicroProfile apps for the Cloud
01h 21mTips, Tricks and Workarounds with Jakarta EE/MicroProfile
53mJakartaEE and Eclipse MicroProfile coexist in WildFly
47mDream Team Jakarta EE + MicroProfile
35mOptimize your applications to the max with Jakarta EE and MicroProfile
46mQuo vadis JEE?
47mJakarta EE + MicroProfile: The Nonfunctional Features #slideless.