From Java EE to Jakarta EE: a user perspective
summary
An account of the Java EE to Jakarta EE shift that names concrete moves: Oracle stops proprietary stewardship, the project moves to the Eclipse Foundation governance, specification ownership becomes project-based, and certification shifts to self-certification to lower legal and cost barriers. Runtime work shows Open Liberty and TomEE as viable implementations and MicroProfile already delivers 6 releases / 5+ implementations. Remaining risks are execution of the new spec process and convincing cloud-native developers with faster startup and smaller footprints.
AI-written summary · about
chapters (11)
- 0:00Jakarta EE transition intro
- 2:36Java EE evolution review
- 5:50Innovation vs standardization
- 10:50Oracle’s shift and Eclipse role
- 12:55Eclipse governance model
- 15:08Comparison with Java Community Process
- 17:38Jakarta EE execution challenges
- 19:50Open Liberty runtime
- 21:40Modernization hurdles
- 24:09Developer focus and cloud
- 25:56Jakarta EE future outlook
related talks
32mFrom Legacy to Legendary: Jakarta EE’s Evolution in the Modern Era
50mOpening Up Java EE: Panel Discussion with
40mJakarta EE and Cloud Native Projects at Eclipse Foundation
42mWhat's Going on With Jakarta EE
34mJakarta EE: The Future of Cloud Native Java is Open!
46mOpening Up Java EE: Panel Discussion with Oracle, IBM, Red Hat, and the Eclipse Foundation
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE
06mInterview with