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 2017/09/20 15:15:01 UTC
[jira] [Created] (ISIS-1730) Invoking an action button which was
rendered enabled but which is actually disabled at point of invocation
throws stacktrace.
Dan Haywood created ISIS-1730:
---------------------------------
Summary: Invoking an action button which was rendered enabled but which is actually disabled at point of invocation throws stacktrace.
Key: ISIS-1730
URL: https://issues.apache.org/jira/browse/ISIS-1730
Project: Isis
Issue Type: Bug
Components: Core: Viewer: Wicket
Affects Versions: 1.15.0
Reporter: Dan Haywood
Priority: Minor
Fix For: 1.16.0
For example, if the domain object is rendered and then some other user changes its state such that an action is no longer available.
The framework *does* correctly re-check the state of the action, but if now found to be disabled then we get a stack trace rather than - say - a toast pop-up with the reason that the action can no longer be invoked.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)