-
Bug
-
Resolution: Done
-
Major
-
4.2.0.Final
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?
- clones
-
JBIDE-18994 Unexpected JAX-RS validation error for client filters
- Closed
- is cloned by
-
JBIDE-25669 Unexpected JAX-RS validation error for Feature
- Resolved
-
JBIDE-21985 Unexpected JAX-RS validation error for client filters
- Closed