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

[jsr339-experts] Re: Updated Client API and Interceptors/Filters proposal is available - please review

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

On 06/09/2011 06:01 PM, Bill Burke wrote:
>
>
> On 6/9/11 8:53 AM, Marek Potociar wrote:
>>
>>
>> On 06/06/2011 02:06 PM, Bill Burke wrote:
>>>
>>>
>>> On 6/6/11 7:45 AM, Dionysios G. Synodinos wrote:
>>>> - I don't like all the getFeature() methods. Just have a
>>>> getProperties() method and be done with it. I don't think I've ever
>>>> seen such an API in Java EE before or what you're trying to
>>>> accomplish with it.
>>>>
>>>>
>>>> I appreciate simplicity, but semantically "properties" continue to be
>>>> quite different to me than "features".
>>>>
>>>
>>> I just don't see a use case for being able to see if a feature is enabled or enabling or disabling a feature at the
>>> Invocation level. Can somebody provide one?
>>>
>>
>> How about:
>>
>> postPersonalData.disableFeature(Features.REQUEST_LOGGING);
>>
>
> You wouldn't do this at runtime.

Can you please elaborate why? Suppose I want to log/audit all communication except for the initial handshake message
containing some confidential data. It would be natural to simply disable the logging just for that single invocation IMHO.

Marek