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

[jsr339-experts] Re: properties, Invocation, Client, and Resource

From: Marek Potociar <marek.potociar_at_oracle.com>
Date: Thu, 09 Jun 2011 13:35:37 +0200

All right, please disregard my previous message. Did not notice the additional thread that was already started for this
message due to some weird grouping of emails into threads in my mail client. What I am asking was already answered in
the thread.

Marek

On 06/09/2011 01:32 PM, Marek Potociar wrote:
> Hi Bill,
> I think I understand. We do similar thing in Jersey - client properties are propagated to web resource and then to
> request. Those properties can be overridden or updated at each level. This is also the intended behavior for the
> proposed JAX-RS client API.
>
> Apart from a proper javadoc, do you see anything else that we should do in this respect?
>
> Marek
>
> On 06/08/2011 12:51 AM, Bill Burke wrote:
>> One thing I've found a need for is for interceptors to be able to access properties set on the Client and/or WebResource
>> instance. For example a digital signature interceptor would want access to the private key to sign a request with. A
>> private key might be set for each request, or might be set as a default property on the Client (or WebResource).
>>
>> The way I've done it within Resteasy is that each Invocation/ClientRequest's property map is a copy of the Client's
>> property map. Then, the interceptor only has to access the Invocation's property map and will either get something
>> specific to the request, or defaulted at the Client level.
>>
>> Get what I'm saying? Or is my explanation horrible?
>>
>>