[jax-rs-spec users] Re: JAX-RS 2.1 - work schedule

From: Pavel Bucek <>
Date: Fri, 13 Jan 2017 09:40:13 +0100

Hi Adam,

I will send an email about that later today, my change is going through
internal review.

Currently, API-wise, there always is rx(...) method overload with
ExecutorService as a parameter, so it is definitely possible to
configure it this way. Using provider is not a bad idea - let's get back
to this during the review (I'm wiring that down). I will need to look at
where else could client use it; async() is the obvious one.

I found your issue (, no
need to file it again. I already tagged it as "2.1-candidate", which
means that I believe we should include it in next release. Let's see how
the review will go and if we can solve JAX_RS_SPEC-523 quickly, it could
be the next thing on our agenda.

Thanks and regards,

On 13/01/2017 08:09, Adam Bien wrote:
> Hi Pavel,
> is the repo with your PoC already online somewhere?
> In all client and server parts relying on thread pools, the ExecutorService instance should be configurable (via provider and parameter passing). With that we get integration with Java EE application servers and Concurrency Utilities.
> This is a big deal in Microservice architectures (Bulkheads etc.)
> I already filed an issue last year, should I re-file it?
> cheers,
> adam
>> On 11 Jan 2017, at 22:17, Pavel Bucek <> wrote:
>> Dear experts,
>> thanks for your warm welcome!
>> Let's kick this off with the work schedule. As mentioned in the renewal ballot, we have following three big features we want to deliver:
>> - Reactive client API
>> - Server Sent Events support (server and client)
>> - Non-blocking I/O
>> Since we already have proposal for the first two, I believe we should start with them - to finish them off and then continue with non-blocking I/O.
>> As Santiago mentioned, the schedule is pretty aggressive and we need to see how fast this will go. After we are done with these "bigger" tasks, we will go through backlog items, fitting as much as we can into this release.
>> So what's going to happen next? We are currently working in PoC implementation of Reactive client API which is currently in the JAX-RS source repository master branch - it is almost ready for review. We identified small improvement needed there and I'm going to take care of that, finish the PoC implementation and document the API on the wiki. Once this is done, I'll send a request for review to this mailing list.
>> Please let us know if you have any comments, questions or suggestions.
>> Thanks and regards,
>> Pavel