Tomcat 11 and Jakarta EE 11
summary
Tomcat 11 implements Jakarta EE 11 for Servlet, JSP, EL, WebSocket, Annotations and Authentication, passes the EL and WebSocket TCKs with Servlet and JSP in final ballot, and sets Java 17 minimum. The spec removes the security manager and long‑deprecated APIs, adds clarified header and path canonicalization rules, consistent file upload exception behavior, and a safe HTTP session accessor for WebSocket. New Tomcat features include OpenSSL via FFM (Java 22+), virtual thread support, automatic TLS cert reloading and a rate‑limit filter.
AI-written summary · about
chapters (21)
- 0:00Introduction and speaker background
- 0:55Jakarta EE 11 overview
- 2:21Security manager removal
- 3:03Deprecated APIs cleanup
- 3:47Servlet specification changes
- 6:40Session access outside request cycle
- 7:26HTTP/2 server push deprecation
- 8:55Early hints in Servlet
- 9:15JSP and Expression Language updates
- 9:38Expression Language improvements
- 11:02WebSocket session handling
- 12:46Annotations and authentication changes
- 13:09Tomcat implementation progress
- 14:54New features in Tomcat 11
- 15:38Removed features in Tomcat 11
- 17:22RFC compliance updates
- 18:25Logging and access log enhancements
- 19:09Security hardening updates
- 20:54Miscellaneous improvements
- 21:14Performance with Foreign Function Memory
- 22:18Virtual threads benefits
related talks
38mApache Tomcat: New and Upcoming
32mPrepare for Jakarta EE 11!
44mPaving the road with Jakarta EE and Apache TomEE
51mJakarta EE 10 and Beyond
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE
50mBoost Your Performance and Developer Productivity with Jakarta EE 11
32mWrap-Up
44mJakarta EE 11 - Performance and Developer Productivity