What Every Spring Developer Should Know About Jakarta EE
summary
Spring and Jakarta EE are tightly coupled: Spring Framework 6 already relies on Jakarta 9/10 APIs and Spring Framework 7 targets Jakarta 11, with Jakarta 11 using Java 17/21 and more than half the specs updated. Demos show a Spring Boot web app running on Open Liberty (Tomcat optional) and a Jakarta app using Jakarta Data mirroring Spring Data. Integration examples work both ways: a CDI producer exposes a Spring AI bean to Jakarta, and a CDI bean can be looked up from Spring to call a Jakarta AI model. Jakarta 12 is planned for 2026.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:05Java EE and Spring history
- 6:56Jakarta EE core concepts
- 12:07Jakarta EE for Spring
- 13:55Servlets and Spring integration
- 16:45Demo: Spring Boot on Open Liberty
- 19:36Jakarta EE specs used by Spring
- 22:03Jakarta Data vs Spring Data
- 23:28Demo: Jakarta Data in Spring-like app
- 27:49Jakarta specs consumed by Spring
- 28:31Spring AI in Jakarta EE
- 33:16Demo: Spring AI in Jakarta EE app
- 37:56Jakarta EE in Spring
- 38:17Demo: Jakarta EE AI from Spring
- 42:39Jakarta EE and Spring timeline
- 45:11Summary and future
- 46:36Q&A
related talks
02h 38mJakarta in 2023, What Is the Situation?
58mJakarta EE Meets AI
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE
50mBoost Your Performance and Developer Productivity with Jakarta EE 11
44mJakarta EE 11 - Performance and Developer Productivity
48mJakarta EE 10 Feature by Feature
48mA Developer's Guide to #JakartaEE 11
46mJakarta EE 11: Going Beyond the Era of Java EE