@RegisterProvider on a sub-resource

[mkonzal]

I would like to register different Providers on different sub-resources, which take a precedence (have higher priority) over registration on the upper level in case of conflict.

There is no concrete information about it in the MP specification, just general information

In addition to defining providers via the client definition, interfaces may use the @RegisterProvider annotation to define classes to be registered as providers in addition to providers registered via the RestClientBuilder.

Resource proxy

@Path("/foo")
@RegisterProvider(XYZWriter.class)
@RegisterProvider(XYZReader.class)
public interface Foo {
    @POST
    @Consumes("xyz")
    @Produces("xyz")
    FooResponse get(FooContent content);

    @Path("/bar")
    Bar getBar();
}

Sub resource proxy

@RegisterProvider(ABCReader.class)
public interface Bar {
    @POST
    @Produces("abc")
    BarResponse get();
}

Expectation

foo.getBar().get();

will use ABCReader as MessageBodyReader.

Currently on most MP rest client implementations only registrations on the resource proxy are done.

[andymc12]

Sorry for the long delayed response. This definitely sounds like a nice feature to add to a future release of the spec. Thanks for opening this issue!