Guidelines on how to implement support of Reactor Mono and Flux into RestEasy Client

[soft4rchitecture]

At our company we'd need to integrate Mono and Flux types in a Java Interface and use the RESTEasy Proxy Framework to generate a client implementation using those types.
For this to work, we'd need RESTEasy to support Reactor (Mono and Flux).
Ref: https://docs.jboss.org/resteasy/docs/3.6.2.Final/userguide/html/Reactive.html#d4e2161
jar 'org.jboss.resteasy:resteasy-reactor' already supports the loading of FluxRxInvokerProvider and MonoRxInvokerProvider, but then the MessageBodyReaders fail and many more problems might lie ahead.

Would any of you have any guidelines on how to do it? is there a method to add support for a new reactive types ?
Thnaks a lot

[jamezp]

What kind of failures are you seeing? I'd highly suggest using a minimum of RESTEasy 5.0.4.Final (Jakarta REST 2.1) or 6.2.1.Final (Jakarta REST 3.1). Are you running in a specific container like WildFly or JBoss EAP?

[soft4rchitecture]

Thanks a lot for your valuable time

[soft4rchitecture]

Hey, i'm writing a PR and i'll keep you updated on the status. Seems to be a bug but i'm not sure yet

[jamezp]

It looks like there is no MessageBodyWriter or MessageBodyReader for these and it expects the usage of a RxInvoker. I'm not too familiar with this library, however what might need to be done is maybe a new annotation like @RxInovker(MonoRxInvoker.class) for the target proxy.

[soft4rchitecture]

actually it’s probably a bug. I’m posting an issue and a PR along with it on tomorrow.
Roughly speaking, reactive type Publisher is exepected when the proxy framework parses the Java interface description. but Mono is written instead, so the control flow goes completely off track with invalid errors.

[jamezp]

Ah nice catch @soft4rchitecture! Much appreciated.