Re: Ajax busy indicator getting stuck
Created WICKET-4257 with quickstart.
2011/11/19 Igor Vaynberg igor.vaynb...@gmail.com:
that might work.
-igor
On Fri, Nov 18, 2011 at 1:45 PM, Nazaret Kazarian
nazaret.kazar...@gmail.com wrote:
Yep, I will create a quickstart and create a jira.
If it turns out to be a bug, until it gets solved, I am thinking of
showing / hiding the busy indicator using js pre/post call handlers.
And maybe also use the following code as a condition in post call
handler to hide the indicator:
wicketAjaxBusy: function() {
for (var c in Wicket.channelManager.channels) {
if (Wicket.channelManager.channels[c].busy) {
return true;
}
}
return false;
}
Do you think that's a good idea?
2011/11/18 Igor Vaynberg igor.vaynb...@gmail.com:
quickstart, jira?
-igor
On Fri, Nov 18, 2011 at 1:20 PM, Nazaret Kazarian
nazaret.kazar...@gmail.com wrote:
That sounds reasonable. According to the scenario I described above,
the indicator will always get stuck if you use channel type Drop and
issue an ajax request on a busy channel.
2011/11/18 coincoinfou olivierandr...@gmail.com:
Same problem with IndicatingAjaxLink when I switch to
AjaxChannel.Type.DROP
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Ajax-busy-indicator-getting-stuck-tp4082837p4083026.html
Sent from the Users forum 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
-
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
-
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
Ajax busy indicator getting stuck
Hi, I have added a global ajax indicator to all my pages by having all pages (through a TemplatePage superclass) implement the IAjaxIndicatorAware interface. Generally it works, but I have noticed that it is quite easy to get the ajax indicator stuck spinning indefinitely, by issuing many ajax calls quickly the one after the other. For example if I press an ajax button multiple times quickly the busy indicator gets stuck. It seems as if the Wicket.show(hide)Incrementally js functions lose count of ajax requests and the busy indicator is never actually hidden. Has anyone encountered this problem? Thanks a lot Naz - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax busy indicator getting stuck
I have also noticed that with 1.5.3... I normally block the page with div to prevent this but for links on a modal window it happens to me (because blocking div is behind modal). Regards, Ernesto On Fri, Nov 18, 2011 at 11:53 AM, Nazaret Kazarian nazaret.kazar...@gmail.com wrote: Hi, I have added a global ajax indicator to all my pages by having all pages (through a TemplatePage superclass) implement the IAjaxIndicatorAware interface. Generally it works, but I have noticed that it is quite easy to get the ajax indicator stuck spinning indefinitely, by issuing many ajax calls quickly the one after the other. For example if I press an ajax button multiple times quickly the busy indicator gets stuck. It seems as if the Wicket.show(hide)Incrementally js functions lose count of ajax requests and the busy indicator is never actually hidden. Has anyone encountered this problem? Thanks a lot Naz - 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
Re: Ajax busy indicator getting stuck
On Fri, Nov 18, 2011 at 12:59 PM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: I have also noticed that with 1.5.3... I normally block the page with div to prevent this but for links on a modal window it happens to me (because blocking div is behind modal). And you didn't experience this with 1.5.2 ? Maybe https://issues.apache.org/jira/browse/WICKET-4071 is involved ? Regards, Ernesto On Fri, Nov 18, 2011 at 11:53 AM, Nazaret Kazarian nazaret.kazar...@gmail.com wrote: Hi, I have added a global ajax indicator to all my pages by having all pages (through a TemplatePage superclass) implement the IAjaxIndicatorAware interface. Generally it works, but I have noticed that it is quite easy to get the ajax indicator stuck spinning indefinitely, by issuing many ajax calls quickly the one after the other. For example if I press an ajax button multiple times quickly the busy indicator gets stuck. It seems as if the Wicket.show(hide)Incrementally js functions lose count of ajax requests and the busy indicator is never actually hidden. Has anyone encountered this problem? Thanks a lot Naz - 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 -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax busy indicator getting stuck
Martin, Before switching to 1.5.3 I was working with 1.5.x trunk and I think it was the same there... but I can´t say that assertion is 100% true. As said in my case this happens to me on a modal window because my indicator panel blocks the UI and that blocking div is behind the modal. It should not be very difficult to produce a quick-start for this issue (I guess). Best regards, Ernesto On Fri, Nov 18, 2011 at 12:02 PM, Martin Grigorov mgrigo...@apache.org wrote: On Fri, Nov 18, 2011 at 12:59 PM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: I have also noticed that with 1.5.3... I normally block the page with div to prevent this but for links on a modal window it happens to me (because blocking div is behind modal). And you didn't experience this with 1.5.2 ? Maybe https://issues.apache.org/jira/browse/WICKET-4071 is involved ? Regards, Ernesto On Fri, Nov 18, 2011 at 11:53 AM, Nazaret Kazarian nazaret.kazar...@gmail.com wrote: Hi, I have added a global ajax indicator to all my pages by having all pages (through a TemplatePage superclass) implement the IAjaxIndicatorAware interface. Generally it works, but I have noticed that it is quite easy to get the ajax indicator stuck spinning indefinitely, by issuing many ajax calls quickly the one after the other. For example if I press an ajax button multiple times quickly the busy indicator gets stuck. It seems as if the Wicket.show(hide)Incrementally js functions lose count of ajax requests and the busy indicator is never actually hidden. Has anyone encountered this problem? Thanks a lot Naz - 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 -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.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
Re: Ajax busy indicator getting stuck
I'm sorry I forgot to mention that I am using version 1.4.19 With a little reverse engineering I noticed that maybe one of the cases this happens is this: an ajax button is pressed, showIncrementally is executed, but the actual ajax request is postponed because its channel is busy. When the time comes to actually execute the request, the request is stopped because of precondition check, and thus hideIncrementally is never called. This loses the count. A fix might be to call hideIncrementally when the ajax request precondition is not met. As to why the precondition is not met, I am guessing it's because the previous ajax request did DOM replacement in a way that the precondition of the queued request is no longer met. 2011/11/18 Ernesto Reinaldo Barreiro reier...@gmail.com: Martin, Before switching to 1.5.3 I was working with 1.5.x trunk and I think it was the same there... but I can´t say that assertion is 100% true. As said in my case this happens to me on a modal window because my indicator panel blocks the UI and that blocking div is behind the modal. It should not be very difficult to produce a quick-start for this issue (I guess). Best regards, Ernesto On Fri, Nov 18, 2011 at 12:02 PM, Martin Grigorov mgrigo...@apache.org wrote: On Fri, Nov 18, 2011 at 12:59 PM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: I have also noticed that with 1.5.3... I normally block the page with div to prevent this but for links on a modal window it happens to me (because blocking div is behind modal). And you didn't experience this with 1.5.2 ? Maybe https://issues.apache.org/jira/browse/WICKET-4071 is involved ? Regards, Ernesto On Fri, Nov 18, 2011 at 11:53 AM, Nazaret Kazarian nazaret.kazar...@gmail.com wrote: Hi, I have added a global ajax indicator to all my pages by having all pages (through a TemplatePage superclass) implement the IAjaxIndicatorAware interface. Generally it works, but I have noticed that it is quite easy to get the ajax indicator stuck spinning indefinitely, by issuing many ajax calls quickly the one after the other. For example if I press an ajax button multiple times quickly the busy indicator gets stuck. It seems as if the Wicket.show(hide)Incrementally js functions lose count of ajax requests and the busy indicator is never actually hidden. Has anyone encountered this problem? Thanks a lot Naz - 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 -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax busy indicator getting stuck
Martin, WICKET-4071 is not involved as I am not using AjaxIndicatorAppender in any way. 2011/11/18 Nazaret Kazarian nazaret.kazar...@gmail.com: I'm sorry I forgot to mention that I am using version 1.4.19 With a little reverse engineering I noticed that maybe one of the cases this happens is this: an ajax button is pressed, showIncrementally is executed, but the actual ajax request is postponed because its channel is busy. When the time comes to actually execute the request, the request is stopped because of precondition check, and thus hideIncrementally is never called. This loses the count. A fix might be to call hideIncrementally when the ajax request precondition is not met. As to why the precondition is not met, I am guessing it's because the previous ajax request did DOM replacement in a way that the precondition of the queued request is no longer met. 2011/11/18 Ernesto Reinaldo Barreiro reier...@gmail.com: Martin, Before switching to 1.5.3 I was working with 1.5.x trunk and I think it was the same there... but I can´t say that assertion is 100% true. As said in my case this happens to me on a modal window because my indicator panel blocks the UI and that blocking div is behind the modal. It should not be very difficult to produce a quick-start for this issue (I guess). Best regards, Ernesto On Fri, Nov 18, 2011 at 12:02 PM, Martin Grigorov mgrigo...@apache.org wrote: On Fri, Nov 18, 2011 at 12:59 PM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: I have also noticed that with 1.5.3... I normally block the page with div to prevent this but for links on a modal window it happens to me (because blocking div is behind modal). And you didn't experience this with 1.5.2 ? Maybe https://issues.apache.org/jira/browse/WICKET-4071 is involved ? Regards, Ernesto On Fri, Nov 18, 2011 at 11:53 AM, Nazaret Kazarian nazaret.kazar...@gmail.com wrote: Hi, I have added a global ajax indicator to all my pages by having all pages (through a TemplatePage superclass) implement the IAjaxIndicatorAware interface. Generally it works, but I have noticed that it is quite easy to get the ajax indicator stuck spinning indefinitely, by issuing many ajax calls quickly the one after the other. For example if I press an ajax button multiple times quickly the busy indicator gets stuck. It seems as if the Wicket.show(hide)Incrementally js functions lose count of ajax requests and the busy indicator is never actually hidden. Has anyone encountered this problem? Thanks a lot Naz - 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 -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax busy indicator getting stuck
Same problem with IndicatingAjaxLink when I switch to AjaxChannel.Type.DROP -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-busy-indicator-getting-stuck-tp4082837p4083026.html Sent from the Users forum 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
Re: Ajax busy indicator getting stuck
That sounds reasonable. According to the scenario I described above, the indicator will always get stuck if you use channel type Drop and issue an ajax request on a busy channel. 2011/11/18 coincoinfou olivierandr...@gmail.com: Same problem with IndicatingAjaxLink when I switch to AjaxChannel.Type.DROP -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-busy-indicator-getting-stuck-tp4082837p4083026.html Sent from the Users forum 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
Re: Ajax busy indicator getting stuck
quickstart, jira? -igor On Fri, Nov 18, 2011 at 1:20 PM, Nazaret Kazarian nazaret.kazar...@gmail.com wrote: That sounds reasonable. According to the scenario I described above, the indicator will always get stuck if you use channel type Drop and issue an ajax request on a busy channel. 2011/11/18 coincoinfou olivierandr...@gmail.com: Same problem with IndicatingAjaxLink when I switch to AjaxChannel.Type.DROP -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-busy-indicator-getting-stuck-tp4082837p4083026.html Sent from the Users forum 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax busy indicator getting stuck
Yep, I will create a quickstart and create a jira.
If it turns out to be a bug, until it gets solved, I am thinking of
showing / hiding the busy indicator using js pre/post call handlers.
And maybe also use the following code as a condition in post call
handler to hide the indicator:
wicketAjaxBusy: function() {
for (var c in Wicket.channelManager.channels) {
if (Wicket.channelManager.channels[c].busy) {
return true;
}
}
return false;
}
Do you think that's a good idea?
2011/11/18 Igor Vaynberg igor.vaynb...@gmail.com:
quickstart, jira?
-igor
On Fri, Nov 18, 2011 at 1:20 PM, Nazaret Kazarian
nazaret.kazar...@gmail.com wrote:
That sounds reasonable. According to the scenario I described above,
the indicator will always get stuck if you use channel type Drop and
issue an ajax request on a busy channel.
2011/11/18 coincoinfou olivierandr...@gmail.com:
Same problem with IndicatingAjaxLink when I switch to AjaxChannel.Type.DROP
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Ajax-busy-indicator-getting-stuck-tp4082837p4083026.html
Sent from the Users forum 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
-
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
Re: Ajax busy indicator getting stuck
that might work.
-igor
On Fri, Nov 18, 2011 at 1:45 PM, Nazaret Kazarian
nazaret.kazar...@gmail.com wrote:
Yep, I will create a quickstart and create a jira.
If it turns out to be a bug, until it gets solved, I am thinking of
showing / hiding the busy indicator using js pre/post call handlers.
And maybe also use the following code as a condition in post call
handler to hide the indicator:
wicketAjaxBusy: function() {
for (var c in Wicket.channelManager.channels) {
if (Wicket.channelManager.channels[c].busy) {
return true;
}
}
return false;
}
Do you think that's a good idea?
2011/11/18 Igor Vaynberg igor.vaynb...@gmail.com:
quickstart, jira?
-igor
On Fri, Nov 18, 2011 at 1:20 PM, Nazaret Kazarian
nazaret.kazar...@gmail.com wrote:
That sounds reasonable. According to the scenario I described above,
the indicator will always get stuck if you use channel type Drop and
issue an ajax request on a busy channel.
2011/11/18 coincoinfou olivierandr...@gmail.com:
Same problem with IndicatingAjaxLink when I switch to AjaxChannel.Type.DROP
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Ajax-busy-indicator-getting-stuck-tp4082837p4083026.html
Sent from the Users forum 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
-
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
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
