Re: ListenerInvocationNotAllowedException in wicket 6.19

2015-04-15 Thread Martin Grigorov
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 wrote: > Looks like there was a problem with non-printable character in HTML. > If it doesn't show up again - that's it, solve

Re: ListenerInvocationNotAllowedException in wicket 6.19

2015-04-15 Thread ssamarin
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 Users

Re: Client side javascript listeners / HeaderItems / OnDomReadyHeaderItem

2015-04-15 Thread Patrick Davids
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 'ondomready',

Re: ListenerInvocationNotAllowedException in wicket 6.19

2015-04-15 Thread Martin Grigorov
Hi, On Wed, Apr 15, 2015 at 2:04 PM, ssamarin wrote: > 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. > There must be some JS error if the components are not refresh

Re: ListenerInvocationNotAllowedException in wicket 6.19

2015-04-15 Thread ssamarin
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 c

Re: Client side javascript listeners / HeaderItems / OnDomReadyHeaderItem

2015-04-15 Thread andrea del bene
On 15/04/2015 11:02, Patrick Davids wrote: 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, befor

How to get a map of parameters of a request in wicket 6

2015-04-15 Thread David Kaufman
Hi, In Wicket 1.4 we have following code snippet: final Map 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 Set parameterNames = getRequest().g

Client side javascript listeners / HeaderItems / OnDomReadyHeaderItem

2015-04-15 Thread Patrick Davids
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

Re: Veil on ajax which ends with redirect eventually

2015-04-15 Thread Martin Grigorov
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 loadi

Veil on ajax which ends with redirect eventually

2015-04-15 Thread tomask79
Hi guys, in our wicket application we use standard framework mechanism for showing veil on Ajax actions by implementing the interface IAjaxIndicatorAware. It's working fine until you've got situation when your on event method of Ajax form component, for example, ends with setResponsePage redir