Re: Remove obsolete RxJava code and keep RxJava2 only one

I was just about to remove the optional marking on reactive streams, and noticed that rxjava was still around. I guess it was decided to keep it? I'll point out, this now makes the dependency chain even harder to follow (since rxjava2 uses reactive streams, but rxjava does not). John On Wed,

[GitHub] johnament closed pull request #377: 2.6.x fixes

johnament closed pull request #377: 2.6.x fixes URL: https://github.com/apache/cxf/pull/377 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to

Re: Reactive Streams dependency in Project Reactor module

Hi John I think I indeed sent some confusing messages yesterday :-) OK, what I meant was that the module had the original code to do with supporting the client only Rx invocations (such a client code can be server scoped as in your example), and the server only invocations (Json subcriber).

Re: How to use rx() with proxy clients?

The two lasts options sounds the most natural to me and the first one can be emulated with the second one propably. AFAIK the async is only supported by having an InvocationCallback which means you put in the request context an instance from an interceptor currently in the proxy API - don't think

Re: [VOTE] CXF 3.2.2

+1 Thanks Alessio On Fri, Feb 2, 2018 at 8:57 PM, Daniel Kulp wrote: > This is a vote to release CXF 3.2.2. We’ve fixed over 60 JIRA issues, > definitely time to release it. This also includes releases of build-utils > (3.4.0) and xjc-utils (3.2.1) to allow it to build on