Hi Martin,
I tried to use the quickstart-app to reproduce the issue but I can't
login with the provided username/password combination. I looks like the
credentials are correct in the AdminUser-fixture script. Do I need to
start the user seed somehow?
Erik
On 12/11/2015 04:33 PM, Erik de Hair wrote:
On 12/09/2015 08:31 PM, Martin Grigorov wrote:
Hi Erik,
What kind of button is this ?
To me it looks like this is the "OK" button from the
ActionParametersFormPanel.java, i.e. the OK button for a Modal window
where
you enter the parameters for an @Action
(org.apache.isis.viewer.wicket.ui.components.actions.ActionParametersFormPanel.ActionParameterForm#addButtons).
Line"boolean succeeded =
actionExecutor.executeActionAndProcessResults(target, form);" is
responsible to call your action method. I don't see how this code
will be
executed if there is an error like the one below.
Please try to reproduce it in a mini app.
Ok, I'll try to do that.
Thank you!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, Dec 9, 2015 at 8:53 AM, Erik de Hair <e.deh...@pocos.nl> wrote:
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
