@Path annotation not used if inherited from an interface

The @Path annotation is not used if it is inherited from an interface.

Example for a base interface:

@Path("/persons")
public interface PersonResource {
}

The client interface now inherits from the above one:

@RegisterRestClient(configKey = "person-service")
public interface PersonService extends PersonResource {
}

This will lead to the following (wrong) call:

http://localhost:8080/whatever

Adding a superfluous @Path on the rest client interface makes it work correctly:

@Path("/persons")
@RegisterRestClient(configKey = "person-service")
public interface PersonService extends PersonResource {
}

This will lead to the following (correct) call:

http://localhost:8080/persons/whatever

The expected behaviour would be, that the @Path annotation is correctly used from the parent interface and there is no need to duplicate it.

[andymc12]

Hi @michael-schnell , thanks for opening this issue. We try to follow JAX-RS’s lead where possible, and in section 3.6 of the JAX-RS Spec, it talks about annotation inheritance - specifically:

JAX-RS annotations may be used on the methods and method parameters of a super-class or an implemented interface. Such annotations are inherited by a corresponding sub-class or implementation class method provided that the method and its parameters do not have any JAX-RS annotations of their own. Annotations on a super-class take precedence over those on an implemented interface. The precedence over conflicting annotations defined in multiple implemented interfaces is implementation specific. Note that inheritance of class or interface annotations is not supported.

So for MP Rest Client, implementations should support annotation inheritance on methods, but not on interfaces.

That said, I don’t see that this is documented in the MP Rest Client specification - and I don’t think there are any TCK tests for this. So, if you don’t mind, I’d like to keep this issue open to clarify this behavior in the spec/TCK.

Thanks again!

[CENGOiSM]

I am facing the same issues right now. Searching for a solution I found that annotating @Provider on the implemented class is solving the mentioned problems. What do you think about this approach, am I missing something?

@Path("/persons")
public interface PersonResource {
}

@Provider
public class PersonResource implements PersonResource {
}