On 14 Mar 2014, at 6:42 PM, Guy Rouillier <guy.rouillier_at_gmail.com> wrote:
> We encountered the same issue. The simplest solution is to move your interfaces to a different package. That was a better solution for us in the long run anyway; we exported the interface package to a client JAR to be used with the client proxy.
Am I right in understanding that if jersey finds a concrete class, and the class implements a given interface with the required annotations, jersey will just "do the right thing" and treat the annotations as if they had been applied directly to the concrete class, interface and concrete class just need to be in different packages?
Regards,
Graham
--