Eleventh Time's the Charm - From J2EE to Jakarta 11
summary
A 1999-era EJB app is packaged unchanged and runs on WildFly 26 and on a modern WildFly/OpenLiberty Jakarta EE 11 server, proving practical backward compatibility; the talk demos a hello/world EJB demo and shows OpenRewrite for the Jakarta rename work. Jakarta EE 11 adds Java 17/21 features such as records as embeddables, an enum value converter, getSingleResultOrNull, CDI alignment, and conditional virtual threads via managed executor virtual=true. Jakarta Data 1.0 is stateless and currently disallows lazy relations.
AI-written summary · about
chapters (19)
- 0:00Introduction and speaker background
- 1:05J2EE origins and complexity
- 3:13EJB 2.1 demo and legacy code
- 6:04Backwards compatibility in Jakarta EE
- 8:09Java EE 5 improvements and Spring influence
- 11:04CDI vs EJB perceptions
- 13:16Timeline of Java EE evolution
- 14:23MicroProfile emergence and purpose
- 16:58MicroProfile as addition to Jakarta EE
- 18:25Transition to Jakarta EE and renaming
- 21:41Jakarta EE 10 CDI alignment
- 24:57Jakarta EE 11 new features
- 26:19Records and JPA enhancements
- 29:07Virtual thread support in Jakarta EE
- 31:43Jakarta Data specification
- 33:35Competition with Spring ecosystem
- 37:31Why Jakarta EE 11 is the charm
- 40:05MicroProfile vs Jakarta EE clarification
- 41:11Q&A session
related talks
50mBoost Your Performance and Developer Productivity with Jakarta EE 11
44mJakarta EE 11 - Performance and Developer Productivity
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE
48mJakarta EE 10 Feature by Feature
46mThe Evolution of Enterprise Java with Jakarta EE 11 and Beyond
45mEverything YOU need to Know About Jakarta EE 10
32mPrepare for Jakarta EE 11!
44mThe Past, Present, and Future of Enterprise Java