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

[jsr339-experts] Re: [jax-rs-spec users] Re: setting request properties disrupts fluent api

From: Bill Burke <bburke_at_redhat.com>
Date: Thu, 25 Oct 2012 10:20:47 -0400

On 10/25/2012 10:02 AM, Marek Potociar wrote:
>
> On Oct 25, 2012, at 3:51 PM, Bill Burke <bburke_at_redhat.com> wrote:
>
>> configuration() doesn't really belong or is needed on Invocation.Builder. Add property() and remove configuration() entirely, or at least move it to Invocation.
>
> Just to better understand your motivation:
>
> So you say there's no use case for having a different configuration (other than properties) on a per-request bases if the requests are targeted at the same resource (say a need to have special filters for a hand-shake request but not for the other ones)?
>

Meh, maybe you're right...but instead of Configuration maybe just add
proeprty()/register() methods to Invocation.Builder and move
configuration() to Invocation

interface Invocation.Builder {
     Builder property(String name, Object value);
     Builder register(Class<?> clazz);
     Builder register(Object instance);
...
}

> Also, what is your use case for modifying properties? Would it make sense to implement that use case via features or provider instances?
>

Specifying request QoS properties, like how long you want to wait for a
response. Setting a Public/PrivateKey or other objects that might be
used by a filter/interceptor.

Bill

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com