Maybe we - core devs - should email about the major changes we are doing in svn/ Wicket 2.0. It's all still very alpha though at this stage.
Also, we could /consider/ putting those methods back in with final (so your code will break) and a deprecation message? Or should we just settle for search (/replace) facilities being good enough for the job and list what needs to be changed. And of course, once Johan and Igor are done with the model changes, they will add a section to http://wicket-wiki.org.uk/wiki/index.php/ Migrate-2.0 Eelco On Jun 16, 2006, at 4:16 AM, Mark Derricutt wrote: > Just a heads up for anyone playing with HEAD/Wicket 2.0, one sneaky > little trap I just found is that the Model class has changed its > method signature from: > > public Object getObject(Component component) > > to > > public Object getObject(); > > Anywhere I was extending Model this tripped up silently by -adding- > my (now) overloaded getObject() method. On the one or two > instances where I was using AbstractReadOnlyModel (which doesn't > provide a standard getObject() method) this signature change was > trippedup and lead to finding this breakage. > > Just a heads up for anyone else dipping there toes.... > > -- > i like my video games - mamma said they are gonna melt my brains > i like my video games - i don't care what daddy said; they're my > reality > - henning pauly > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
