Skip to content

Jakarta REST 4.0 Discussion (EE 11)

Jump to bottom
Santiago Pericasgeertsen edited this page Jul 28, 2021 · 1 revision

About this page

Use this page to discuss proposals for Jakarta REST 4.0 API. The primary goal of this release is to drop support for @Context and use CDI exclusively for all the injection needs. This will be a non-backward compatible version of Jakarta REST.

Scopes for Resources and Providers

There's some consensus that by default all resource classes should be @RequestScoped and that all provider classes should be @ApplicationScoped. What other scopes are supported? Can Application subclasses be anything but @ApplicationScoped?

Scanning of Resources and Providers

CDI enables scanning of resources and providers. There have been some discussions about how CDI and Jakarta REST applications should interact (See https://github.com/eclipse/microprofile/issues/50), but very little consensus. Is there still a need for Application subclasses in this version? Should implementations simply scan for resources and providers and automatically collect them? If both mechanisms are supported, how should they interact?

Clone this wiki locally