your perception of our convention is wrong. the things we make final by default are the things we do not expect to be overridden/subclassed by our users.
-igor On Dec 11, 2007 9:43 PM, Kent Tong <[EMAIL PROTECTED]> wrote: > > > Eelco Hillenius wrote: > > > > Does anyone disagree with this > > https://issues.apache.org/jira/browse/WICKET-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel? > > > > I personally prefer not marking classes as final unless necessary. However, > AFAIK the wicket > convention is the opposite: marking them as final by default. Now what is > being suggested > seems to be contradictory to your project convention. In that case I must > say that is a > bad thing. > > > > ----- > -- > Kent Tong > Wicket tutorials freely available at http://www.agileskills2.org/EWDW > -- > View this message in context: > http://www.nabble.com/anyone-disagree--tp14268271p14289410.html > Sent from the Wicket - Dev mailing list archive at Nabble.com. > >
