[jbosstools-issues] [JBoss JIRA] (JBIDE-25669) Unexpected JAX-RS validation error for Feature

Cody Lerum (JIRA) issues at jboss.org
Fri Jan 26 17:42:00 EST 2018


Cody Lerum created JBIDE-25669:
----------------------------------

             Summary: Unexpected JAX-RS validation error for Feature
                 Key: JBIDE-25669
                 URL: https://issues.jboss.org/browse/JBIDE-25669
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: webservices
    Affects Versions: 4.2.0.Final
            Reporter: Cody Lerum
            Assignee: Xavier Coulon


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
(v7.5.0#75005)


More information about the jbosstools-issues mailing list