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 that's in JIRA. John On Wed, Mar 21, 2018 at 7:18 PM James Carman <ja...@carmanconsulting.com> wrote: > 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, Mar 21, 2018 at 6:38 PM John D. Ament <johndam...@apache.org> > wrote: > > > 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 the various docs to list it out, that there are > > different dependencies now for RxJava and RxJava2. RxJava2 is built on > > Reactive Streams, and there's a common CXF dependency used for Reactive > > Streams in Project Reactor and RxJava2 support. However, because of > > RxJava1 support I couldn't just bring this in. So I ended up pushing > > forward on a split of the two modules. > > > > Do you in fact use both RxJava and RxJava2? Or just RxJava2 support? > > > > John > > > > On Wed, Mar 21, 2018 at 5:53 PM James Carman <ja...@carmanconsulting.com > > > > wrote: > > > > > 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 > > > > > >
