. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 25.2. Put models and page data in fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 25.9. Validators must not change any data or models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 25.10 . . . . . . . . . . . . . . . . . . . . . . . 283 25.11. Use the Wicket session only for global data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 25.12. Do

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 25.2. Put models and page data in fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 25.9. Validators must not change any data or models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 25.10 . . . . . . . . . . . . . . . . . . . . . . . 282 25.11. Use the Wicket session only for global data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 25.12. Do

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 25.2. Put models and page data in fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 25.9. Validators must not change any data or models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 25.10 . . . . . . . . . . . . . . . . . . . . . . . 295 25.11. Use the Wicket session only for global data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 25.12. Do

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 25.2. Put models and page data in fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 25.9. Validators must not change any data or models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 25.10 . . . . . . . . . . . . . . . . . . . . . . . 294 25.11. Use the Wicket session only for global data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 25.12. Do

getModel(). A model can be shared among diferent components. ● With models our components can handle data without knowing how they are physically persisted or retrieved. ● Up to Wicket 7, a model was a public void setObject(final Object object); } Model in Wicket ● A model is a facade for the data object that a component must display (for example with a label) or set (for example with a textfeld) according to properties name: Data model: Display data model: ● CompoundPropertyModel can drastically improve the code of our example form if we use the form itself as data object. Example form: second