Jakarta EE Meets AI
summary
Jakarta EE 11 updates target Java 21 compatibility, introduce Jakarta Data, make CDI more central, and split into core profile (released December), web profile (released April) with the full platform expected in June; release delays stem from refactoring the 30-year-old TCK to JUnit/Arquillian. Demos show concrete integrations: calling OpenAI via REST from pure Jakarta, using Spring AI (worked but Spring 3.3.9 conflicts with Java 24), Quarkus and Helidon examples, and a LangChain4j path—each approach builds working endpoints and returns model content.
AI-written summary · about
chapters (13)
- 0:00Java and Jakarta EE history
- 3:36Jakarta EE evolution
- 7:10Jakarta EE 11 updates
- 10:44Jakarta EE tech overview
- 17:55AI integration in Java
- 20:23Spring AI demo
- 26:46Quarkus AI integration
- 30:00Pure Jakarta EE AI demo
- 39:18LangChain for Java demo
- 42:35CDI for AI integration
- 45:05Using Spring AI in Jakarta
- 52:34Helidon AI integration
- 55:24Jakarta EE 11 wrap-up
related talks
45mJakarta EE Meets AI
46mJakarta EE 11: Going Beyond the Era of Java EE
44mJakarta EE 11 - Performance and Developer Productivity
32mPrepare for Jakarta EE 11!
43mPrepare for Jakarta EE 11!
49mWhat Every Spring Developer Should Know About Jakarta EE
48mJakarta EE 10 Feature by Feature
51mJakarta EE 10 and Beyond