Hi, > ofcourse it is up to the user what to do there. > But if you would ask certain persons i think they would say make it final ;) well, the whole point of providing a isEnabled() method for AttributeModifiers / behaviours is about overriding it so you could enable/disable it depending on some application logic (which could make sense in my opinion). So making it final would be quite the same as not providing enabling of behaviours, because an behaviour is pretty much able to disable itself by some internal logic at any point...
> The final keyword is again discussed at JavaPolis (ofcourse :)) To quote the xom guy: classes should be final by default in java because you need to design for overriding. I'm tempted to agree on that one :) Ralf ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
