Paving the road with Jakarta EE and Apache TomEE
summary
Explains how the javax→jakarta namespace change and Java SE 11 support in Jakarta EE 9.1 affect real apps, and shows three practical paths: a bytecode converter that turns an old WAR into a jakarta WAR (demo converts a sample WAR in milliseconds and decompiles to jakarta.servlet.), the Apache Tomcat migration tool and forked Eclipse Transformer as Maven plugins that produce dual binaries, and the TomEE Maven plugin* for running migrated apps on a TomEE (TomEE is TCK‑certified Jakarta EE 9.1 web profile). Notes remaining manual fixes (POM updates, JSF3 + annotated datasource quirks) and recommends CI/CD to be ready for Jakarta EE 10.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:45Welcome
- 2:00Context
- 5:16Impact
- 13:50Demo
- 21:25Eclipse Transformer
- 26:50Source Code Migration
- 30:45Apache TomEE
- 32:54TomEE Maven
- 39:32Recommendations
- 40:06How to contribute
- 41:07Challenges
- 41:52Tools
- 42:18Wrap up
related talks
39mJakarta EE 9 and Beyond
43mJakarta EE 9 and Beyond
45mEverything YOU need to Know About Jakarta EE 10
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE
49mHow to Easily Upgrade to Jakarta EE 10 Javax to Jakarta Prefix without a Hassle
42mWhat's Going on With Jakarta EE
48mJakarta EE 10 Feature by Feature
40mMigrating from Java EE to JakartaEE 10: Challenges and Opportunities