You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2011/03/24 22:04:05 UTC

[jira] [Resolved] (WICKET-3553) Reset the busy flag in Wicket.Channel if the execution of the callback fails for some reason

     [ https://issues.apache.org/jira/browse/WICKET-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-3553.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-RC3
                   1.4.17

Improved with r1085142 (trunk) and r1085143 (1.4.x)

> Reset the busy flag in Wicket.Channel if the execution of the callback fails for some reason
> --------------------------------------------------------------------------------------------
>
>                 Key: WICKET-3553
>                 URL: https://issues.apache.org/jira/browse/WICKET-3553
>             Project: Wicket
>          Issue Type: Improvement
>    Affects Versions: 1.4.16, 1.5-RC2
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>             Fix For: 1.4.17, 1.5-RC3
>
>
> If a scheduled (in Wicket.Channel) callback fails for some reason (in my case because WicketAjaxDebug was not yet loaded) then the 'busy' flag for the channel remains 'true' until the page is reloaded.
> It would be better to try/catch the execution of the callback and reset the flag in case of an error.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira