Port rest-data-panache to RESTEasy Reactive

[geoand]

Description

quarkus-rest-data-panache currently depends on RESTEasy Classic.
We should port this to RESTEasy Reactive.
This won't be trivial as RESTEasy Reactive builds all the necessary information by looking at the Jandex index of existing code, while rest-data-panache generates code which isn't available at this point.

Implementation ideas

No response

[quarkus-bot]

/cc @FroMage, @loicmathieu, @stuartwdouglas

[loicmathieu]

I'm not convinced by this one.
Maybe we need to create a rest-data-panache-rx based on RestEasy reactive and provides both flavor.
Rest-data-panache is opinionated, and provides easy to use REST endpoints based on conventions for quick usage, advanced use case will not use it so accoring to me having it using the simpliest extensions is OK.

As I understand it, soon, resteasy classic will be based on resteasy reactive so this may not be very important.

[geoand]

I'm not convinced by this one.
Maybe we need to create a rest-data-panache-rx based on RestEasy reactive and provides both flavor.
Rest-data-panache is opinionated, and provides easy to use REST endpoints based on conventions for quick usage, advanced use case will not use it so accoring to me having it using the simpliest extensions is OK.

Agreed. But the base itself provides no additional features. The under the covers transition to RESTEasy Reactive should be absolutely transparent (apart from the different transitive dependencies).
rest-data-panache-rx wouldn't provide anything different. What am talking about here is simply swapping the underlying REST layer.
From a user perspective there should be no change at all.

As I understand it, soon, resteasy classic will be based on resteasy reactive so this may not be very important.

Not true. What will happen likely is that we will be proposing resteasy-reactive as the default API layer.

[geoand]

Closed by accident, so I am reopening