I'd like to chime in on the conservative side here. I believe you should only introduce a completely new way of doing things if there is a CLEAR benefit to be had. Color me unconvinced on that account. Furthermore, annotations on classes are basically equivalent to tagging interfaces. I thought those were bad?
Thomas > -----Original Message----- > From: Eelco Hillenius [mailto:[EMAIL PROTECTED] > Sent: Donnerstag, 10. Januar 2008 18:23 > To: [email protected] > Subject: Re: 1.4/2.0 annotations support > > > - @Stateless - instead of overriding isStateless > > - @Headers - define headers specific for the page > > Playing the advocate of the devil: the thing with those is > that it doesn't actually solve anything. I mean, you hardly > decrease the lines of code you have to write to achieve > something, annotations are arguably harder to discover than > overridable methods, and we end up with having multiple ways > to do the same thing... > > Eelco >
