[CAUSEWAY-1730] Invoking an action button which was rendered enabled but which is actually disabled at point of invocation throws stacktrace.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.15.0
• Fix Version/s: 1.16.0
• Component/s: Viewer Wicket
• Assignee: Daniel Keir Haywood
• Reporter: Daniel Keir Haywood
• Created: 20/Sep/17 15:14
• Updated: 08/Jan/18 19:54
• Resolved: 29/Dec/17 13:58

Description

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.

Issue Links

• Blocked: CAUSEWAY-1803 Hitting escape twice on prompt results in the error page.