I mean to have the timer attached to a component that is a sibling of the tab. You could register component as listener of this behavior and have the timer ask the components if the have changes to "repaint".
I´m not sure but the problem you have might happen as follows: 1-When you switch tabs you stop the behavior at server side. 2-On client side there is a queued AJAX request (timer) asking to refresh a component. 3-When tab is switched the component the "timer" is trying to address is no longer on the path specified by the request. If timer is on a sibling f the tab this will not happen. Ernesto On Mon, Jun 7, 2010 at 9:16 PM, Decebal Suiu <decebal.s...@asf.ro> wrote: > > Thanks, I will try. The problem with your approach is that in our application > each tab is a "section" that can be added using spring framework (modular > architecture). For example the dashboards tab has many widget panels, each > widget panel is auto refreshable (different time for different widget). Also > each tab supports contributors (you can add panels, fragments that can be > auto refreshable). I think that will be better to stop/remove behaviors > automatically on tab switch and not to force each contributor to do it. > What's mean for you "outside" the tab? > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/TabbedPanel-with-AjaxSelfUpdatingTimerBehavior-tp2243691p2246419.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
