I'm not proposing to ease up on final in general, though I think using finals aggressively makes more sense when the project is taking shape and less so when things got more stabilized. Components like Link, TextField, CheckBox, ImageButton are components people regularly ask about why they can't override onComponentTag(Body) on the lists or on IRC, and tbh I wouldn't know. People can mess up for sure, but otoh if you're know what you're doing it makes perfect sense sometimes. There are a lot of places where it is easy to come up with good arguments on why you want to hide/ protect certain code, but onComponentTag(Body) on most of our core components imho are not.
Eelco On 12/6/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
And what is the reason why you want to remove final? What are the use cases? I understand your words, but just removing final to remove final, IMO is not a good idea. I don't mind though to relax our general position on removing final for these two methods if there is real use case. I still think the fairly strikt approach we took at the beginning served us very well. Juergen
