> And killing the onDetach() for subclasses could be bad in the future. Yeah, we should only finalize such things if it would be plain wrong if sub classes would implement that, which is not the case here.
If you want to ensure no subclass ever messes up the call to onDetach, we can always finalize onDetach, and let that method class onDetached or whatever new, empty method would come in place. That's protective but messes up the API a bit. So alternatively you could say, well, this is not that common of a use case, if people want to extend and override onDetach, they just should take care of calling super. Eelco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
