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 turned out, the namespace changes rippled throughout the entire Java ecosystem and Spring was no exception since it incorporates and builds on a lot of the Jakarta EE APIs and technologies. This means that it is a great advantage for a Spring developer to be aware of what is going on with the Jakarta EE specifications.
Looking at it from the other way around, Jakarta EE benefits a lot from looking at what Spring Framework does. The Jakarta EE specifications can pick up and standardize technologies and practices that have been made industry standard by Spring Framework. Jakarta Data is an example of this.
Come to this session to learn why Spring matters to Jakarta EE as well as how Jakarta EE matters to Spring!