Re: JSR311: _at_Target of FIELD for _at_*Param annotations

From: Bill Burke <>
Date: Mon, 10 Mar 2008 11:39:54 -0400

Marc Hadley wrote:
> On Mar 7, 2008, at 3:21 PM, Bill Burke wrote:
>> Marc Hadley wrote:
>>> What I want to avoid is using the annotations defined in JSR 311 in
>>> places not covered by the spec because that could be quite confusing
>>> for developers. I'm less worried about a meta-annotation since those
>>> are generally hidden from developers.
>> I understand your fear, but having two sets of annotations is even
>> more confusing for a vendor's implementation.
> Why ? I want crisp semantics for the annotations defined by the spec and
> I think non-portable innovations belong in a vendor-specific package.
> That way its easy for developers to see when they are using portable vs
> non-portable functionality.
>> Let us innovate.
> That's hardly fair, nothing is stopping you innovating.

Sure it is. I want to use @*PARAM on fields, for resource classes,
MessageBodyReader/Writers, and mapping POJO parameters. Now, because
you're refusing to change the @Target, I either have to scrap it, or
have a parallel *exact* annotation hierarchy.


Bill Burke
JBoss, a division of Red Hat