Pedro, Thank you.
This is indeed a solution, but it would mean rewriting the whole application. There are lots of components that need to be refreshed, and adding to each of them the behavior don't seem trivial. I'll give it a try anyway. Thank you Ale On Thu, Oct 1, 2009 at 1:17 PM, Pedro Santos <pedros...@gmail.com> wrote: > I have a page that's refreshing its components every n seconds using > AbstractAjaxTimerBehavior. > Among these components there's a list of links. > > Would be nice if you apply AbstractAjaxTimerBehavior only to components > that > need to be updated. Than you don't get in trouble with your links... > > On Thu, Oct 1, 2009 at 7:45 AM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Is blocking the page with a "veil" while refreshing a valid solution? > That > > way users could not click on links while the page is refreshing... > > > > Best, > > > > Ernesto > > > > On Thu, Oct 1, 2009 at 12:37 PM, Alessandro Novarini < > > a.novar...@sourcesense.com> wrote: > > > > > Hello everybody, > > > > > > I've just subscribed to this ml, and even thou I searched past mails > > about > > > my problem, I couldn't find any hint. > > > > > > I have a page that's refreshing its components every n seconds using > > > AbstractAjaxTimerBehavior. > > > Among these components there's a list of links. > > > > > > If I try to click a link near the refresh interval, the request get > lost > > > because of the refresh. > > > > > > One of the solution I'm trying is to disable the refresh on the > > > onMouseDown, > > > and re-enabling it on the onMouseUp event, but this doesn't work as the > > > first event stops forever the ajax method call (the refresh). > > > > > > Every kind of help will be really appreciated :) > > > > > > Thank you in advance > > > Ale > > > > > > > > > -- > Pedro Henrique Oliveira dos Santos >
