Hi,
Indeed, creating a new module specifically for RxJava is technically
clean, but creating it for a code which no one will probably use and
also adding one module to the large number of CXF modules, with only 2/3
Java files :-) is a bit problematic...
I guess I can keep it as is in 3.2.x but remove it once a new master
opens...
Thanks, Sergey
On 15/11/17 16:04, John D. Ament wrote:
What about just leaving the old RxJava code in a module by itself (when I
was looking recently, it didn't make much sense to see both RxJava and
RxJava2 in one module).
On Wed, Nov 15, 2017 at 10:56 AM Sergey Beryozkin <sberyoz...@gmail.com>
wrote:
Hi
cxf-rt-rs-extension-rx ships the code for both (old) RxJava and RxJava2
code. It supports returning RxJava2 Flowable and Observable on the
server and accepting it on the client, and the same for the (old) RxJava
Observable...
While even the (old) RxJava code is very new for CXF, the reality is
that RxJava has been around for a while now and with RxJava2 embracing
org.reactivestreams, it's hard to see CXF users preferring to start with
the (old) RxJava.
The other minor problem is that cxf-rt-rs-extension-rx has optional
RxJava and RxJava2 deps to be able to ship the relevant code in the same
module and splitting it into 2 modules will be too much at this point.
I suggest that unless some users confirm (I CC to the users) that they
need to use the (old) RxJava code, then we just remove it and make
things much simpler...
Thanks, Sergey
