cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Begg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DOSGI-267) ContainerRequestFilter intents do not get registered as providers
Date Wed, 24 May 2017 00:12:04 GMT

     [ https://issues.apache.org/jira/browse/DOSGI-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Richard Begg updated DOSGI-267:
-------------------------------
    Attachment: use_provider_annotation.patch

Sample patch to use the @Provider annotation to determine if an intent is a 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
>            Priority: Minor
>         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.3.15#6346)

Mime
View raw message