On Mar 8, 2013, at 5:42 PM, Marek Potociar <marek.potociar_at_oracle.com> wrote:
> On Mar 8, 2013, at 4:52 PM, Marek Potociar <marek.potociar_at_oracle.com> wrote:
>
>> On Mar 7, 2013, at 11:34 PM, Bill Burke <bburke_at_redhat.com> wrote:
>>
>>> #1 Do you really want somebody calling replaceWith() within Feature.configure() or DynamicFeature.configure()? IMO, replaceWith() should be moved to ClientBuilder, Client and WebTarget and not be part of Configurable. (Or even removed from the API and deferred to a later release)
>>
>> I'm fine with making it part of client component APIs. I'm strongly against removing from the API. Your issue has been targeted for 2.0.
>
> FWIW, I'd be happy to remove the Configurable support from Invocation.Builder and Invocation. After working with the API for quite some time now my feeling is that in these two cases we went just too far. I have not run into a single use case where I would need to configure these types. And I find it annoying that the IDE code completion offers me these methods when I do not need them at all.
>
> What do you think? I know, it's a major change though...
FYI: Filed a new issue for your reference:
http://java.net/jira/browse/JAX_RS_SPEC-385
Marek