It's sometimes quite handy to be able to split resources into an interface annotated as root resource and a concrete implementing class.
As an example:
This is working fine so long as you manually configure HelloResourceImpl as a root resource class, but using Jersey's otherwise so convenient PackagesResourceConfig to automatically scan in specific packages (say in this case com.bar) for resources will ignore HelloResourceImpl.
ScanningResourceConfig only looks for @Path or @Provider annotations inside the actual classes themselves. While it is possible to overload the @Path annotation (or any other JAX RS annotation) in the concrete implementation, it kind of beats the purpose, scattering the resource configuration across multiple locations.
It would be great if ScanningResourceConfig were to either look for some new type targeting annotation, such as @Resource, that could be used to manually annotate root resource classes even if they do not themselves have the @Path annotation. Better yet of course, would be to inspect all classes found in the specified resource packages more thoroughly and see not only if they implement @Path directly but whether they implement any interfaces which in turn are annotated with @Path.