> 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...
I agree 100% *except* the real point of annotations is to provide *meta-data* about your objects. So the question is whether or not these "settings" are meta-data about a page? Overriding methods does accomplish the same goal, but it's a very different approach. I'm all for whatever makes the most sense. I personally think the @Stateless annotation would kick ass. =)
