When the @Cache annotation is set on an interface, in as sub-resource, the annotation is not detected by the CacheControlFeature, and as a consequence, no cache-control header is set on the GET request.

This issue stems from the change in the behavior of ResourceInfo, brought by https://issues.redhat.com/browse/RESTEASY-2391

Indeed, the CacheControlFeature was relying on the resourceInfo.getMethod() to hold the annotation, which is no more the case, because this now returns the implementation method, which is not necessarily the annotated one.

This issue not only affects CacheControlFeature but also any dynamic feature which relied on the previous behavior of resourceInfo.