Well, most of the time in wicket you don't update models. You pull data from models, and that's also how you need to implement them. The exception is of course when you process a form, in that case you push data into models, which in turn update your beans, etc. But most of the time (when rendering page/components) everything is pull.
-Matej On 10/12/07, Per Newgro <[EMAIL PROTECTED]> wrote: > Hi *, > > i come from building swing applications - component oriented with MVC. > There we build a chain of components (Frames and panels which contains > panels). The Controller in main panel communicates with database to get the > data to represent. To get reusability the parent of a component sets data to > child and so on. So we push the models downstairs. > > Is there a wicket way in achieving this? Afaik setModel only sets the model > of its component. I'm looking for an easy way to refresh the models of the > childs. Because wicket is making many things different (no critism - it's ok > for me) - maybe you do this different to. > > Thanks for helping me out > Per > -- > Psssst! Schon vom neuen GMX MultiMessenger gehört? > Der kanns mit allen: http://www.gmx.net/de/go/multimessenger > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
