[
https://issues.apache.org/jira/browse/ISIS-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16306292#comment-16306292
]
ASF subversion and git services commented on ISIS-1730:
-------------------------------------------------------
Commit ffa5f5fc3ad30a150e3ddb66e522556d3e6f749e in isis's branch
refs/heads/master from [~danhaywood]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=ffa5f5f ]
ISIS-1730 and ISIS-1803: catches ListenerIInvocationNotAllowedException to
render a better message
for both thes cases.
> 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
> Assignee: 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)
