We have been using the quarkus-rest extension (Quarkus Resteasy Reactive) as the server framework for our Quarkus services. Plus, we also use the openapi plugin to read one spec file for each service, and generate the JAX-RS API for our services. So, then Quarkus implements this generated API using the above mentioned quarkus-rest extension.

Recently, this extension changed how to interpret the string query params, so regardless whether a query param is not set, or is set to empty, it will return null (more info in here).

The change became a blocker for us because we have some enum types that need to interpret the string values specified at the API query param to map the value with the enum value “EMPTY” (see for example: BillingProviderType).

As a solution for this blocker, one solution is to assess if we can replace the quarkus-rest extensions by the quarkus-resteasy extensions:

As part of the SWATCH-3469, we identified some tasks that need to be done before this migration. Each of these tasks are items for this epic.

Spike document: https://docs.google.com/document/d/1HDAV_BklIlbSE9gS8tPIF_jpiDPwsSNdvJukaqld6PU/edit?usp=sharing