Re: RxJava Observable with CXF

FYI, I moved the RxJava code into cxf-rt-rs-extension-rx as it is expected to grow Sergey On 01/09/16 21:48, Sergey Beryozkin wrote: Hi I believe it has to be "/cxfdemo" as opposed to "/cxfdemo/*", autoconfigurer set a correct servlet pattern itself, though may be it should recognize the

Re: RxJava Observable with CXF

Hi I believe it has to be "/cxfdemo" as opposed to "/cxfdemo/*", autoconfigurer set a correct servlet pattern itself, though may be it should recognize the custom property already has it... Sergey On 01/09/16 17:53, Muse Mekuria wrote: Hi Sergey, I've been trying to setup very simple

Re: RxJava Observable with CXF

Hi Sergey, I've been trying to setup very simple spring boot setup with the jax-rs starter in order to try the RxJava updates and I'm having trouble getting it to work. Not sure what I'm missing but everything I tried gives me a 404. I've looked at JAX-RS Spring Boot Scan

Re: RxJava Observable with CXF

I've looked a bit more today into it, see http://git-wip-us.apache.org/repos/asf/cxf/commit/1224d5cc It does offer a much better integration with JAX-RS 2.0 AsyncResponse, see a test there which streams the subscription items as get available which is quite useful. AsyncResponse itself can do

Re: RxJava Observable with CXF

Great! I'll be looking forward to this. Muse On Tue, Aug 30, 2016 at 1:04 PM, Sergey Beryozkin wrote: > This should address this issue: > > http://git-wip-us.apache.org/repos/asf/cxf/commit/502db47a > > More work will be done on the client side too later on, with >

Re: RxJava Observable with CXF

This should address this issue: http://git-wip-us.apache.org/repos/asf/cxf/commit/502db47a More work will be done on the client side too later on, with CompletableFuture to be supported OOB. Sergey On 30/08/16 09:47, Sergey Beryozkin wrote: Hi Muse Thanks for starting experimenting with

Re: RxJava Observable with CXF

Hi Muse Thanks for starting experimenting with it. It is fair to say that this feature requires more work - it is being planned. I'll add a missing @Provider annotation and that alone will let this provider be auto discovered too with CXF 3.1.8 (with a cxf.jaxrs.classes-scan -