We do this, although have a few places where we mark a component dirty manually (obscure change in model etc).
We use an identity hash map to record components considered dirty then a simple algorithm to remove descendants of already dirty components. Wicket is not great for getting this to work as I couldn't find good hooks to monitor changes in enabled, children etc... The dirty list is stored in WebRequestCycle so it gets cleaned out every request. I've raised this topic a few times if you want to look at previous threads. Artur W. wrote: > > Hi! > > I have complex dependencies between components on my page. > e.g. when user clicks on a button coupe of other components change. > > Now I refresh them with AjaxRequestTarget and a lots of conditions. > Is it possible that Wicket automatically adds dirty component to the > AjaxRequestTarget.addComponent(...)? > > > Thanks for help, > Artur > -- View this message in context: http://www.nabble.com/Component-autorefresh-with-Ajax-tf4691652.html#a13411063 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
