Update the server to use RESTEasy Reactive

Description

Accordingly, to @geoand, applications using quarkus-resteasy-reactive should still benefit from a better startup time, runtime performance, and memory footprint, even though not using reactive style/semantics. Most importantly, applications using RESTEasy Classic should be able to move to quarkus-resteasy-reactive without any changes to code if they are relying on JAX-RS API.

We should evaluate how much it would take to change the server to use quarkus-resteasy-reactive.

Based on an initial investigation, we should be working on these tasks:

• Change dependencies to quarkus-reactive-resteasy and successfully build the distribution
• Refactor JAX-RS (sub)resources

• • https://github.com/keycloak/keycloak/issues/15443
• • https://github.com/keycloak/keycloak/issues/15374
• • https://github.com/keycloak/keycloak/issues/15450
• • https://github.com/keycloak/keycloak/issues/15525
• • https://github.com/keycloak/keycloak/issues/15810
• • https://github.com/keycloak/keycloak/issues/15811
• • • Make it possible to manipulate the request and the response from the KeycloakContext or just leverage our Resteasy SPI.
• • https://github.com/keycloak/keycloak/issues/15602
• • Review injection points for JAX-RS contextual objects
• • • Remove Realm fields from endpoints and obtain it via KeycloakContext
• • • Make the KeycloakContext the single source of truth for any contextual data
• • Review JAX-RS sub-resources so that they don’t rely on context injection or change how they are created

---

• • Make sure dynamic JAX-RS resources are working with Resteasy Reactive

• Make sure all tests are passing
• https://github.com/keycloak/keycloak/issues/15454
• #15389
• Create a SPI for JAX-RS Resources

• Remove adding JAX-RS resources from JAX-RS Application
• Making JAX-RS resources as providers would benefit from our features capabilities
• Making JAX-RS resources as providers would make it easier to extends ou SPI
• Making JAX-RS resources as providers would make unit test easier
• Abstract how we integrated with the underlying runtime when creating JAX-RS (sub)resources. For instance, resolve JAX-RS resources as CDI beans.

Discussion

No response

Motivation

Benefit from the improvements brought by quarkus-resteasy-reactive and keep the server aligned with Quarkus goals.

Details

No response

[danielFesenmeyer]

I have a question regarding the @Context annotation. We currently use it in custom resource implementation, for injecting JAX-RS Request or HttpHeaders via method parameters.

For example:

@Path("customResource")
public CustomDto customGet(@Context Request request, @Context HttpHeaders httpHeaders) {
    // do stuff with request and httpHeaders
    // ...
}

Will this still be supported in the future?

[pedroigor]

@vmuzikar @danielFesenmeyer It should be lot simpler now as you already have access to the KeycloakSession. See https://github.com/keycloak/keycloak-documentation/pull/1721/files#diff-274488d8bdebf79497daf95b0b287e9e720c816f2d52e2cda9a0255b03639936.

The changes above are still a WIP and are subject to change. For instance, you should get those instances like this https://github.com/keycloak/keycloak/pull/15659.