You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2014/10/09 16:56:33 UTC

[jira] [Resolved] (ISIS-688) Make it possible to configure the Wicket timeout for Ajax calls.

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

Dan Haywood resolved ISIS-688.
------------------------------
    Resolution: Won't Fix

Superceded by ISIS-537.

> Make it possible to configure the Wicket timeout for Ajax calls.
> ----------------------------------------------------------------
>
>                 Key: ISIS-688
>                 URL: https://issues.apache.org/jira/browse/ISIS-688
>             Project: Isis
>          Issue Type: Improvement
>          Components: Viewer: Wicket
>    Affects Versions: viewer-wicket-1.3.1
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>
> Currently, for a long-running operation, we see that Wicket hits some sort of timeout on the Ajax call.  This results in the animated "waiting" veil/overlay being removed, and the action dialog still being presented to the user.  This is confusing; the user doesn't get any hint as to whether the action has succeeded, failed, or (as is actually the case) is still running.
> This ticket is to handle such calls better, somehow, at least from a UI perspective.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)