Interview with
summary
Announces migration of Java EE development into the Eclipse Foundation to enable faster release cadence and community-led decisions; project e4j aims to produce a Java EE-compatible runtime. Concrete changes: e4j 1.0 must pass the Java 8 TCK, TCK moves to Eclipse, Servlet 4.0 brings HTTP/2 server push and ALPN support, and the platform adds JSON-B for POJO↔JSON binding plus a revamped Security API. MicroProfile alignment and version/branding decisions move to a community management committee.
AI-written summary · about
chapters (5)
related talks
34mJakarta EE - Not Your Parents' Java EE
27mFrom Java EE to Jakarta EE: a user perspective
53mJava EE 8 and the Open Future of Java EE - What You Need to Know!
32mJakarta EE Community
40mJakarta EE and Cloud Native Projects at Eclipse Foundation
34mJakarta EE: The Future of Cloud Native Java is Open!
51mJakarta EE 10 and Beyond
42mWhat's Going on With Jakarta EE
