From Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE By Ivar Grimstad

Jakarta EE 9 changed its package namespace from javax.* to jakarta.*. This may sound like a trivial change that mostly affects Jakarta EE. So, why should Spring developers care?
As it turns out, the namespace changes ripple throughout the entire Java ecosystem. And Spring is no exception. Spring Framework 6 and Spring Boot 3 raised their baseline to Jakarta EE 9 API level which is supported by Tomcat 10 and Jetty 11 for example.
Attending this session will teach you how to make this migration as smooth as possible. A live coding demo will take you through the steps involved, and point out where to pay special attention.
We will also briefly examine some of the changes planned for Jakarta EE 11 that will prepare you for what to expect in future versions of Spring. All done with Java 21!

IVAR GRIMSTAD
Ivar Grimstad is the Jakarta EE Developer Advocate at Eclipse Foundation. He is a Java Champion and JUG Leader based in Sweden.
Besides advocating the Jakarta EE technologies, Ivar is contributing to the Jakarta EE specifications as well as being the PMC Lead for Eclipse Enterprise for Java (EE4J). He is also one of the specification leads for Jakarta MVC and represents Eclipse Foundation on the JCP Executive Committee.
Ivar is also involved in a wide range of other open-source projects and communities. He is a frequent speaker at International developer conferences.

[USONOFAV]

The shift from Spring Boot 2.7 with Java 8 to Spring Boot 3 with Java 17 has been nothing short of a nightmare, primarily because of the infuriating switch from 'javax' to 'jakarta'. Whoever made the boneheaded decision to change this was clearly off their rocker.