On 2/3/12 10:00 AM, Santiago Pericas-Geertsen wrote:
>
> On Feb 1, 2012, at 10:36 AM, Bill Burke wrote:
>
>> The binding of providers on the server side for JAX-RS resources is
>> pretty staightforward.
>>
>> It is not so straightforward for Clients though. Should we allow the
>> injection of Client instances? i.e.
>>
>> @Resource Client client;
>>
>> In this case, how would the Client be initialized? With what
>> providers? This is important as there will be client-specific
>> filters/interceptors and server-specific filters/interceptors. This
>> also has an effect on default providers created by the container and
>> how those default providers are registered.
>
> Could you comment on [1] to keep track of this?
>
> -- Santiago
>
> [1] http://java.net/jira/browse/JAX_RS_SPEC-170
>
FYI, I think this is a blocker issue as it will be impossible to support
scanning without some way of designating a filter/interceptor as client
or server only. I made some comments on the issue.
Thanks,
Bill
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com