I don't care about (understand) the pros and cons regarding the constructor change. What Wicket needs is parameterized models (generics). I think you should do what ever it takes to support this in a released version as soon as possible.
/Anders Gabor Szokoli wrote: > On 3/7/07, Korbinian Bachl <[EMAIL PROTECTED]> wrote: >> Also please if you decide to not use the new constructor go on a JDK1.5 solo >> dev path soon > > +1 for this if I understand it right :-) > We are not committed to either version yet, do basic prototypes in > 1.2, but untyped getModel() is getting on my nerves already. (How did > we ever use java without generics?) > I am on principle against severe API changes unless they bring > significant benefits, but do not feel myself competent to judge the > current situation. > > > Gabor Szokoli > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
