Any plans to support rxjava 2.x ?

[asereda]

Hello,

First of all, thank you for this nice integration work (jersey + rxjava).

Would it be possible to add support for rx java 2.0 as well ?

I presume it should be a separate package / module.

Thanks.

[asereda]

In fact, I see you've updated TODO list already ( 3h ago :) )

[alex-shpak]

Hi!

Sure, I just planned to add RxJava 2 support.
For now I think to have transitive dependencies on both versions of RxJava and two features: RxJerseyFeature and ReacivexJerseyFeature corresponding.

[asereda]

While you're at it. Perhaps support generic async return type (also) using:

• ListenableFuture (from Guava)
• CompletableFuture (from Java 8)
• java standard Future

Not everbody uses RX.
What do you think ?

[alex-shpak]

I think I would start with RxJava 2. CompletableFuture is also good option. but i'm not sure if Future is neccesary.

[maarek]

What is the status of RxJava2 support? Complete?

[alex-shpak]

Hi!

RxJava 2 support is implemented for server side, but there is some issues with client side. I think maybe to switch from jersey client to some other implementation.

So if you interested only in server then you can already use it.

[maryokhin]

@alex-shpak A good inspiration would be to look at Apollo, it returns CompletionStage in the client, mostly in the format CompletionStage<Response<JacksonObject>>.

[alex-shpak]

I will check it, thanks :)
Also there is news. new Jersey 2.26 will include RxJava 2 client implementation so there will be some movement soon.

[asereda]

Hello,

What are biggest issues currently to support RxJava2 for jersey client ? The reason I'm asking is because I like the approach of sharing interfaces between server and client in the following manner :

Example

// client definition
@Path("/resource")
interface Resource {
    @GET
     Single<String> get();
}

// server side
class ServerResource implements Resource {
     @Override
    public Single<String> get() {
      return Single.just("Hello");
    }
}

// on the client
Resource  resource = WebResourceFactory.newResource(Resource .class, target);
assertThat(resource.blockingGet()).isEqualTo("Hello");

This is the approach that retrofit library is using, and they do integrate nicely with rx2. However no server side support (like jersey).

What would you recommend for our (possible common) usecase ?

[alex-shpak]

Right now there is implementation for rxjava2 client in Jersey v2.26 which is in beta now, when it will be released I will update client and WebResourceFactory to support it.
Here is pull request for WebResourceFactory: #3544
Also this pull request will be highly usefull: #235

Regarding interfaces - that's also my target. it works now in case if resources are registered manually

resourceConfig.register(ServerResource.class);

You can then use @Remote annotation or WebResourceFactoryPatched to create resource proxy from interface
Unfortunately it doesn't work with automatic discovery. But it will be possible to do with HK2. I'm still looking for good solution.

[asereda]

Unfortunately it doesn't work with automatic discovery. But it will be possible to do with HK2. I'm still
looking for good solution.

Are you referring to the fact that @Path annotation can't exists on both interface and implementation (otherwise jersey complains about identical resources) ?

[alex-shpak]

Yes, I case if you put @Path on both class and interface.

Here is few other cases:

@Path("/path")
interface Resource { ... }
class ResourceImpl implements Resource { ... }

resourceConfig.packages("package.here")

This will not work as excepted because only interface getting registered (because it has @Path annotation) and on request jersey cannot instantiate it.

However this should work

@Path("/path")
interface Resource { ... }
class ResourceImpl implements Resource { ... }

resourceConfig.register(ResourceImpl.class)