resteasy reactive vs resteasy

[V. Sevel]

Hello,

is there a plan to prefer using resteasy reactive over resteasy going foward in the future?

I am doing some experiments with stork, and I see that it is not supporting resteasy classic.

we started switching our pilot application to be resteasy reactive only, and I would rather stay that way, for this applications and the next ones, assuming we can be sure that all non reactive use cases are (or will be) covered with resteasy reactive as well.

is there a plan to make resteasy reactive the standard and recommended approach (and discourage/deprecate the non reactive flavor)?

note: swagger does not seem to like resteasy reactive, and there was some effort lately to get kogito to work well with it as well.

Thansk,

Vincent

[clement escoffier]

Hello,

Yes, the goal is to switch to RESTEasy Reactive as the recommended choice. The reasons are described in Quarkus - RESTEasy Reactive - To block or not to block. RESTEasy Reactive and the Reactive REST clients provide more features than the classic alternatives, and most of the development happens on these projects. As you mentioned, Stork is only integrated with the reactive rest client. 

There are a few issues that still need to be fixed before the actual switch:

- all quickstarts and guides should be migrated (work in progress)

- the SSE behavior is not entirely correct (it was on my todo list, but the duplicated contexts support got the priority)

I cannot give you an ETA, but, following years of experience in guestimates, I would say "soonish". 

Clement

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/d66c42f0-2d72-404d-9bf0-0573e87834f8n%40googlegroups.com.

[V. Sevel]

Thanks Clément.

So we will start switching everything to the reactive flavor, and report the issues we are seeing, if any.

Vincent

[Loïc MATHIEU]

Hi,

As I just stumble upon the issue lately I add one more items to your list Clement ;)

The OIDC token propagation library is also working only for the rest client, not the reactive one. For this use case I think two libraries would need to be created maybe it's a work for @Sergey Beryozkin ...

Regards,

Loïc

To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/82fbcf6e-7ba2-4fe2-a4bf-2df20ae765dcn%40googlegroups.com.

[clement escoffier]

Loic, do you have an issue reported? We have a specific label to track these. 

Clement

To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CAJLxjVGJmH_OGAvyybMn9_ZESe674fJNA5hazaPEaVp-HO%3D-Fw%40mail.gmail.com.

[Loïc MATHIEU]

Just created one: https://github.com/quarkusio/quarkus/issues/23707