Migrating from Java EE to JakartaEE 10: Challenges and Opportunities
Talkat JCON Europe 2023 · on Wednesday, 2023-06-21· at 13:00· Cinema 5, Im Mediapark 1, 50670 Köln, Germany·
summary
Migration is mostly mechanical: change javax. imports and XML namespaces to jakarta., run full integration tests, and fix a few legacy hotspots; OpenRewrite and IDE refactors automate most renames, Eclipse Transformer is an option for bulk changes. Real blockers are third‑party libs and ancient tech (CORBA, old EJBs) and a handful of modules that rely on specific vendor behavior (one Eclipselink JPA module required rewriting annotations to work). Migrations to Payara/WildFly succeed with thorough tests; about half of teams already run Java 17 and Tomcat remains common.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker background
- 2:04Reasons for migrating to Jakarta EE 10
- 4:36Migration approaches and strategies
- 6:25Evolution from Java EE to Jakarta EE
- 9:04Cloud-native focus and Java 21 support
- 10:57Spring and Jakarta EE alignment
- 12:45Current Java and Jakarta EE adoption trends
- 14:09Step-by-step migration process
- 18:30Namespace changes and compatibility
- 26:03Challenges in updating to Jakarta EE
- 31:18Opportunities after migration
- 34:34Automation tools for migration
- 36:00Benefits of latest JDK and tools
- 37:27Summary and closing remarks
related talks
49mHow to Easily Upgrade to Jakarta EE 10 Javax to Jakarta Prefix without a Hassle
44mPaving the road with Jakarta EE and Apache TomEE
32mFrom Legacy to Legendary: Jakarta EE’s Evolution in the Modern Era
48mJakarta EE 10 Feature by Feature
45mEverything YOU need to Know About Jakarta EE 10
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE
55mFrom Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE
51mJakarta EE 10 and Beyond