Hi Andrea,
thanx for your feedback...
Currently I'm researching more into AbstractDefaultAjaxBehaviors.
My javascript which should be executed with priority is an ajax-call.
So, it can be handled by Wicket itself.
I've seen the default event of an AbstractDefaultAjaxBehavior is a
Looks like there was a problem with non-printable character in HTML.
If it doesn't show up again - that's it, solved. Thanks!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/ListenerInvocationNotAllowedException-in-wicket-6-19-tp4670301p4670319.html
Sent from the
Great!
Have fun!
Martin Grigorov
Freelancer, available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, Apr 15, 2015 at 2:58 PM, ssamarin stepan.sama...@gmail.com wrote:
Looks like there was a problem with non-printable character in HTML.
If it doesn't show up
Hi,
Wicket hides the Ajax indicator at onComplete() callback [1].
The redirect is handled either at [2], [3] or [4]. All of those are
processed in the same thread (there is no usage of setTimeout()) so I
think the redirect should happen before the removal of the Ajax indicator.
I guess the
Hi all,
is there something included as feature in Wickets HeaderItems, what I
can use as kind of client-side javascript observer-listener pattern?
For instance... I have components which relies on a on-dom-ready
previous executed javascript, before the components internal javascripts
can be
Hi,
In Wicket 1.4 we have following code snippet:
final MapString, String[] params =
getRequestCycle().getRequest().getParameterMap();
Wicket 6 doesn't have the capabilities of extracting a map. Is this
assumption correct? I can only find a method that extracts the keys:
final SetString
Well,
Behaviour is the following: click once in navigator and wait. Components of
the page are not refreshed at all but component page number is disabled in
background.
Clicking second time on same number in navigator produces an error because
the component is disabled
--
View this message in
