I think especially overriding setHeaders is not intuitive whereas an annotation could really make a difference in readability. But that is a different story.
A simple 1 page guide showing the annotations and their uses is easy enough to put on the web, in the distribution etc. Hibernate/EJB3's annotations are just as hard to discover. But somehow folks do like them. Martijn On Jan 10, 2008 6:22 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > - @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 > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0
