[jira] [Commented] (DOSGI-267) ContainerRequestFilter intents do not get registered as providers

["Christian Schneider (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DOSGI-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082014#comment-16082014 ] 

Christian Schneider commented on DOSGI-267:
-------------------------------------------

I like the idea of using the @Provider annotation as an  indicator that something is a provider type. The problem is that not all existing types might be annotated. So I think it makes sense to combine both approaches.

An object is a provider if it is some known class or if it is annotated with @Provider.


> ContainerRequestFilter intents do not get registered as providers
> -----------------------------------------------------------------
>
>                 Key: DOSGI-267
>                 URL: https://issues.apache.org/jira/browse/DOSGI-267
>             Project: CXF Distributed OSGi
>          Issue Type: Bug
>          Components: provider-rs
>    Affects Versions: 2.1.0, 2.2.0
>            Reporter: Richard Begg
>            Assignee: Christian Schneider
>            Priority: Minor
>             Fix For: 2.3.0
>
>         Attachments: use_provider_annotation.patch
>
>
> Intents of ContainerRequestFilter (or ContainerResponseFilter) type do not automatically get registered as JAX-RS providers in the same way as MessageBodyReader or other provider types.
> This is due to a hard-coded list of classes in the isProvider() method in provider-rs/src/main/java/org/apache/cxf/dosgi/dsw/handlers/rest/RsProvider.java
> Now we could just add the filter classes to the list, but I'm wondering why we don't just look for the @Provider annotation instead?  That way, it should work for everything (assuming people correctly annotate their provider classes).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)