This wouldn't solve the scanning problem. You wouldn't be able to use
scanning if there was a client-only filter/interceptor as that
client-only filter would be registered as a server-side component.
I think a scoping annotation is the way to go.
On 2/15/12 5:40 AM, Marek Potociar wrote:
> I lean towards the option of registering custom Configuration of the
> Target as part of the @Uri annotation somehow (configuration
> provider?). The data from the provided custom configuration instance
> would be used only for initial configuration, IOW the instance would be
> read-only (and thus could be simple).
>
> Marek
>
> On Tue 14 Feb 2012 08:52:39 PM CET, Bill Burke wrote:
>>
>>
>> On 2/14/12 1:54 PM, Santiago Pericas-Geertsen wrote:
>>>
>>> On Feb 14, 2012, at 12:40 PM, Bill Burke wrote:
>>>
>>>>>
>>>>> 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.
>>>
>>> I added a comment as well. I'm trying to understand what is the
>>> environment and scope for this feature. There's two parts: (i) injection
>>> and (ii) configuration. Is injection allowed in all JAX-RS managed
>>> beans, EE managed beans, CDI beans, etc? What is the scope of the class
>>> scanning process? What about a plain SE app?
>>>
>>
>> Its not just an injection issue. If you have a WAR that is scanned, how is the scanner supposed to determine whether
>> a @Provider filter/interceptor should be registered or not? Currently, if you have a client-only filter/interceptor,
>> it *will* be registered autmoatically.
>>
>> Bill
>>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com