A use case depends on what a feature or a property actually shall be.
Currently there is no list of the features, so it is hard to provide use
cases.
> -----Original Message-----
> From: Bill Burke [mailto:bburke_at_redhat.com]
> Sent: Montag, 6. Juni 2011 14:07
> To: jsr339-experts_at_jax-rs-spec.java.net
> Subject: [jsr339-experts] Re: Updated Client API and
> Interceptors/Filters proposal is available - please review
>
>
>
> 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?
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com