Hi Gwyn, > The "Wicket way" would be to decouple the data from the display by > not having each using component having to have it's own model, but by > having a 'parent' model used by both - by default, if the component > itself doesn't have a model, Wicket will look for a model in the > parent, so just set one on the page? And how is the component getting the appropriate property from the hughe model?
I would like to stay a bit more on the component building way. If i have an adress panel on an invoice page and (the same) on an order page, do i have to assume that invoice and order page have the same model to? If they have their own model how can the address panel get the data? Cheers Per -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
