Hi Martin,
On 12/04/2015 02:15 PM, Martin Grigorov wrote:
Hi Erik,
On Fri, Dec 4, 2015 at 2:50 PM, Erik de Hair <e.deh...@pocos.nl> wrote:
ListenerInvocationNotAllowedExceptionBehavior rejected interface
invocation. Component: [AjaxButton [Component id = okButton]] Behavior:
org.apache.wicket.ajax.markup.html.form.AjaxButton$1@7585b8c9 Listener:
[RequestListenerInterface name=IBehaviorListener, method=public abstract
void org.apache.wicket.behavior.IBehaviorListener.onRequest()]
org.apache.wicket.RequestListenerInterface#invoke(RequestListenerInterface.java:237)
This exception means that Wicket cannot execute #onSubmit() method for this
AjaxButton because the button is either disabled or invisible.
So, the button is rendered by Isis/Wicket and *after* that its usability
(visibility and/or enable) is being changed. Clicking on it in the UI makes
a call to the server but Wicket refuses to execute the method.
It does actually completely execute the method.
So you think this could occur when an action is executed for which the
button would be rendered (enabled) before the method was executed, but
would be disabled/hidden after method execution because of changed
object state?
We will need a mini application that reproduces the problem to be able to
help you.
If you expect the above assumption is correct I wil try to reproduce
that scenario.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
