please have a look at the recent checkin / changes messages for model stuff.
there's one more major change i think we should consider for models (i think the rest of it is pretty much there now with my changes today)...
i'd like to make setModel() private if possible. the reason for that is that changing the model of a component once it's constructed leads to all kinds of chaos. basically, i want forms to have their own first class models. and then form components will reference the form's model. but then if you can setModel() on the form, this makes rewiring the formcomponents (which would be wired via PropertyModels to the original form model and not the new one) extremely ugly or impossible. if we instead make setModel() private to Component and only do setModel() in the various Component constructors, it would no longer be possible for people to make this fatal mistake. instead, users would be forced to do the correct thing and change their model's /value/ rather than the model itself by calling setModelObject().
thoughts?
jon
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
