existing functionality should be easy to transition, and the new constructors are all much more typesafe.
any place you were calling a constructor with (name, model, expression), just call (name, new PropertyModel(model, expression))
see checkin message for details on changes and how implicit models (Forms and Pages can have powerful CompountPropertyModels now) can make your life not only easy, but efficient too.
see forminput example for best-practices.
bound models are really only needed when you (a) want full OGNL power to drill down into models or (b) don't want your component properties to have the same name as your component names.
anyway, bound models are not yet demonstrated, but work roughly like this:
BoundCompoundPropertyModel model = new BoundCompoundPropertyModel(beanObject);
model.bind(add(new TextArea("templateInput")), "template");
...
setModel(model);
bindings also permit a class name for use with converters.
i think this is about the usage jan was looking for.
let me know if there are any problems or questions.
best,
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
