On Apr 26, 2010, at 3:28 PM, Laird Nelson wrote:
> I would like to place @Provider on an abstract resource class that
> also happens to implement ContextResolver and thereby indicate that
> all concrete subclasses should be considered to be ContextResolver
> providers.
>
> I see that the @Provider interface is not inherited, but often there
> are requirements in Java EE-land that require various tools to
> consider annotations all the way up the inheritance stack.
>
> So: is @Provider such an exception? If I place it on my abstract
> class, does it effectively mark my concrete classes as providers?
>
No. The annotation is not inherited (does not contain the appropriate
meta-annotation). It needs to be defined on the concrete class.
Paul.