[jax-rs-spec users] Re: Proposal for RX API Improvement

From: Pavel Bucek <>
Date: Fri, 20 Jan 2017 19:29:49 +0100

Hi Marcus,

that was already brought by Adam, just after we started - see

I plan to tackle that right after we are finished with Rx Client and
maybe SSE, since that will most likely have wider impact (not limited to
reactive support) and I'd like to have it made for the whole API at once.

(your code sample does not contain rx() method in the chain - I hope
that's just a typo. I believe when the executor service is set, it
should be used for all async operations, including AsyncInvoker,
RxInvoker and possibly NioInvoker (whatever that will be)).

Best regards,

On 20/01/2017 19:12, Markus KARG wrote:
> Experts,
> the proposed RX API allows to explicitly provide an Executor.
> I assume that typical applications will only use one or two Executors,
> and typically a Java EE application will always use the Default
> Managed Executor Service of the container.
> So maybe it would be a good idea if we can get rid of repeating the
> Executor again and again for each invocation, and provide an optional
> way to set a "Default Executor" directly with the Client instance?
> final Client client = ClientBuilder./newClient/(MY_IO_BOUND_EXECUTOR);
> // /overriding/ implicit default executor
> final CompletableFuture<String> getA ="some uri
> A").request().get(); // /using MY_IO_BOUND_EXECUTOR/
> What do you think?
> -Markus