On Mar 10, 2008, at 11:53 AM, Stephan Koops wrote:
>
>> 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.
> Me too.
I don't want to support @*Param in all those places for the reasons
I've outlined. How do you suggest we make it obvious to developers
that their application is not going to be portable if they choose to
use those annotations in those places ?
Marc.
---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.