Migrating From Spring Boot 2 To Spring Boot 3. What's Jakarta EE Got To Do with It?
summary
Migration requires changing javax to jakarta across app and transitive jars and the demonstration shows the exact steps and tools that make it practical The presenter upgrades a Spring Boot 2 app to Spring Boot 3 while running Java 21 preview features, fixes compilation and failing tests by updating dependencies, uses OpenRewrite for source refactoring and the Eclipse Transformer CLI to rewrite third‑party jars, installs transformed artifacts to the local Maven repo and redeploys to a Jakarta EE 10 runtime like Tomcat 10, after which validation and tests pass and the app runs successfully
AI-written summary · about
chapters (10)
- 0:00Spring Boot 3 migration intro
- 3:55Jakarta EE 9 namespace change
- 6:26Jakarta namespace in Servlets
- 7:53Upgrading Spring Boot 2 to 3
- 12:59Transitive dependencies handling
- 18:41Transforming external libraries
- 24:08Migration steps and Java 21
- 28:44Jakarta EE 11 roadmap
- 31:57Jakarta relevance summary
- 34:41Q&A
related talks
51mHitting the “refresh” button on your Spring web application
50mHow Netflix Is Upgrading to Spring Boot 3
46mNext-Generation Cloud Native Apps with Spring Boot 3
46mBootiful Spring Boot 3.3
48mBootiful Spring Boot: A DOGumentary
28mAutomated Java Upgrades: From Pain to Productivity in 30 Minutes
02h 39mUsing Spring Cloud Data Flow to Run Spring Boot 2.x and 3.x Workloads (Workshop)
01h 00mRefactor your Java EE application using Microservices and Containers