[
https://issues.apache.org/jira/browse/ISIS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908292#comment-13908292
]
Dan Haywood commented on ISIS-688:
----------------------------------
The workaround (of sorts) is to remove long-running synchronous commands, and
instead run them in the background.
In 1.4.0-SNAPSHOT, this can be done either explicitly, by calling the
backgroundService.execute(...), or done implicitly, using
@Command(ExecuteIn.BACKGROUND)
> 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
> Fix For: viewer-wicket-1.5.0
>
>
> 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.1.5#6160)
