Cool, thanks for the info. I’ll update my pom files accordingly tomorrow.
The client proxies could probably work with the invokers, but you’d likely
have to assume you don’t mix rx technologies in your service. Or, perhaps
figure out how to assign the right invoker for each method.
On Wed, Mar
Yes, those dependencies remain the same. But now when you bring in rxjava2
or project reactor they are properly marked as transitive instead of
provided.
I hadn't tried client proxies yet (also a big fan obviously) but suspected
they weren't working with rx functions yet. We should make sure tha
I’m just using RxJava2. Most of that was already in place for 3.2.2,
right? The reactivestreams common module, etc? I like the framework, but
I was unable to use the built-in client stuff, because I’m using client
proxies. I ended up using a custom reader @Provider for the rx types.
On Wed, Ma
Unfortunately, yes.
There was an issue with dependency tress in 3.2.2 with the reactive
modules. TL;DR but you need to depend on rx2 module instead of rx module
(but good news it brings in everything it needs transitively and you can
use an extension to setup the server).
I still need to update
When upgrading from 3.2.2 to 3.2.3, I get the following compilation failure:
package org.apache.cxf.jaxrs.rx2.server does not exist
Is this intended?
James
