Jakarta EE 10 brings a number of updates not only in the Jakarta REST Specification but in other specifications such as Microprofile, too. The Session briefly informs about the new features in Eclipse Jersey, by examples. Jakarta REST 4.0 (planned for Jakarta EE 11) is another major release of the Specification, and unlike the smaller changes in Jakarta 3.1, these changes are rather significant and backward incompatible. The goal of the presentation is to introduce the expected changes in the Specification, and in the Jersey implementation, so that the discussion may start in the community.
For Jersey 3.1, the examples include new HTTP Clients supported by Jersey (Helidon, JDK 11, Apache 5), multipart feature, Java SE Bootstrap API, usage of Microprofile Config & and Microprofile REST client with Jersey, Spring 6 initial support, and CDI support discussion.
The CDI discussion is essential for Jakarta REST 4.0. The DI support will be switched from the custom implementation-specific injection mechanism to CDI / CDI lite. That support results in changes to the API as well as the implementation, and features provided by Jersey. The changes affecting the users are going to be discussed. Other features such as Jakarta Config, CDI-lite supported compile-time injection or multi-application support are also planned for Jersey 4.0.