what bug # is that one?
igor.vaynberg wrote: > > On Sun, Jun 15, 2008 at 11:38 AM, Martin Makundi > <[EMAIL PROTECTED]> wrote: >> Hi! >> >> When I chain components, comboboxes and tables etc., I find myself >> repeatedly solving the same problem: >> * the parent component causes a data reload > > if you chain your models properly (make child's model depend on > parent's model) this should work transparently. > >> * the parent component causes an ajax refresh > > if the parent component repaints itself then all child components are > repainted as well... > >> Has someone found a generic eventlistener-like solution to this? > > there is a patch in jira for a generic event/listener mechanism, but > it wont happen until 1.5 because it requires api breaks. > > -igor > >> >> My current inline implementations have become quite messy to follow >> and I must make some major refactoring soon, as I am beginning to >> understand how the Wicket framework operates - and it would not hurt >> to plug in some neat ready solution you have come up with that keeps >> the code clean and structured. I am thinking something along the lines >> of a hashmap, I would just push the reloaders and refreshers there out >> of sight ... >> >> ** >> Martin >> >> --------------------------------------------------------------------- >> 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] > > > -- View this message in context: http://www.nabble.com/Chaining-components-tp17853298p17859174.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
