jsr370-experts@jax-rs-spec.java.net

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

From: Markus KARG <markus_at_headcrashing.eu>
Date: Wed, 18 Jan 2017 20:04:42 +0100

+1

 

From: Santiago Pericasgeertsen [mailto:santiago.pericasgeertsen_at_oracle.com]
Sent: Dienstag, 17. Januar 2017 16:58
To: jsr370-experts_at_jax-rs-spec.java.net
Subject: Re: [jax-rs-spec users] JAX-RS 2.1 - work schedule

 

 

On Jan 13, 2017, at 6:19 PM, Ondrej Mihályi <ondrej.mihalyi_at_gmail.com> wrote:

 

Actually, I like the unwrap method more than the current proposal. It makes it explicit what I want to get when I write code. The current proposal is similar, but requires me to remember the name of the invoker on top of the rx interface I want to get.

Compare:

Current proposal



CompletionStage<List<String>> cs = client.request()
                .rx(CompletionStageRxInvokerProvider.class)
                .get(new GenericType<List<String>>() {
                });

 Perhaps we should explore turning this into a "real provider”. I.e., something that is registered in the runtime and looked up by the JAX-RS implementation. In which case, the param to rx() could be CompletionStage.class instead. This would be more inline with, say, ParamConverters.

 

— Santiago