Hi! Is it really such a problem to remove the final keyword from Component's getApplication and getRequestCycle? The final was already removed from getSession (see WICKET-426).
So if you won't remove final from these two methods than please make them @Deprecated or remove them completely (as Johan suggests). Should I create a jira issue for this? Thx, Bendis Dne Tuesday 15 of April 2008 10:15:04 Johan Compagner (JIRA) napsal(a): > [ > https://issues.apache.org/jira/browse/WICKET-1533?page=com.atlassian.jira.p >lugin.system.issuetabpanels:all-tabpanel ] > > Johan Compagner closed WICKET-1533. > ----------------------------------- > > Resolution: Won't Fix > > if i want to do something. then it is to remove all those methods from > Component The component interface is polluted because of all those stupid > helper methods. > > You can do what you want as easy in your own RequestCycle and Application > classes: > > class MyRequestCycle > { > static MyRequestCycle get() > { > return (MyRequestCycle)RequestCycle.get(); > } > } > > > Open Component#getApplication and #getRequestCycle for return type > > covariance > > ------------------------------------------------------------------------- > >----- > > > > Key: WICKET-1533 > > URL: https://issues.apache.org/jira/browse/WICKET-1533 > > Project: Wicket > > Issue Type: Improvement > > Components: wicket > > Affects Versions: 1.4-M1 > > Reporter: Martin Benda > > Priority: Minor > > > > It would be nice to be able to override Component's getApplication and > > getRequestCycle to return your own Application or RequestCycle subclass > > to take advantage of Java5 return type covariance. Component#getSession > > is already non-final.
