From Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE
summary
Spring Boot 3 upgrades to the Jakarta EE 9+ APIs so javax -> jakarta breaks appear immediately: compilation errors on imports, failing context-load tests, and runtime mismatches on servlet containers (Tomcat 10+ required). Migration recipe: bump Spring Boot, fix imports with IDE refactor or OpenRewrite, align Jakarta dependency versions, and handle transitive jars by bytecode rewriting with Eclipse Transformer or Apache Tomcat migration tool. Notable wins: UUID as basic type via Jakarta Persistence 3.x (Hibernate 6.2+), and the transformer successfully rewrites compiled libraries so the app runs.
AI-written summary · about
chapters (7)
- 0:00Introduction to Jakarta EE
- 10:32Demo of Spring Boot 2 app
- 16:42Migration to Spring Boot 3
- 26:57Handling transitive dependencies
- 33:02Using Eclipse Transformer
- 40:35Summary and Jakarta EE 11
- 56:05Q&A and resources
related talks
55mFrom Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE
01h 04mMind the Gap: Jumping from Spring Boot 2.x to 3.x
40mMigrating from Java EE to JakartaEE 10: Challenges and Opportunities
49mHow to Easily Upgrade to Jakarta EE 10 Javax to Jakarta Prefix without a Hassle
51mSpring Boot 3 / Spring 6: What’s new?
43mMigrating to Spring Boot 3
49mWhat Every Spring Developer Should Know About Jakarta EE
02h 38mJakarta in 2023, What Is the Situation?