[jbosstools-issues] [JBoss JIRA] (JBIDE-18994) Unexpected JAX-RS validation error for client filters

[Thorsten Kunz (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182101#comment-13182101 ] 

Thorsten Kunz commented on JBIDE-18994:
---------------------------------------

I know this has been closed for quite some time but the very same issues applies to @Provider annotated classes that implement javax.ws.rs.container.DynamicFeature. This should be fine but instead JBIDE is reporting "The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver."
So could you please add javax.ws.rs.container.DynamicFeature to the list of interfaces that would satisfy @Provider annotated class requirements?

Thanks

> Unexpected JAX-RS validation error for client filters
> -----------------------------------------------------
>
>                 Key: JBIDE-18994
>                 URL: https://issues.jboss.org/browse/JBIDE-18994
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: webservices
>    Affects Versions: 4.2.0.Final
>            Reporter: Xavier Coulon
>            Assignee: Xavier Coulon
>              Labels: jax-rs
>             Fix For: 4.3.0.Alpha1
>
>
> We are using JAX-RS client filters in our project. One of the classes looks like this:
> ...
> import java.io.IOException;
> import javax.ws.rs.client.ClientRequestContext;
> import javax.ws.rs.client.ClientRequestFilter;
> import javax.ws.rs.ext.Provider;
> ...
> @Provider
> public class ClientFilter implements ClientRequestFilter
> {
> ...
> }
> The class is part of a Dynamic Web Project with JAX-RS support turned on.
> The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error:
> The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver.
> I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation?



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)