Hi Douglas,
You need to override AbstractDefaultAjaxBehavior#updateAjaxAttributes like
this:
@Override
protected void updateAjaxAttributes(AjaxRequestAttributes attributes)
{
super.updateAjaxAttributes(attributes);
attributes.setThrottlingSettings(new ThrottlingSettings("my-throttle",
Durati
How do you throttle ajax calls in 1.6?
Douglas
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
odd : the maximum value for the timout is Integer.MAX_VALUE.
François
Le 9 juil. 2012 à 15:11, esajjkh a écrit :
> When I create an instance of AjaxSelfUpdatingTimerBehavior with value of
> TIMEOUT, the onPostProcessTarget methods is being called immediately rather
> than it should wait for the
odd : the maximum value for the timout is Integer.MAX_VALUE.
François
Le 9 juil. 2012 à 15:11, esajjkh a écrit :
> When I create an instance of AjaxSelfUpdatingTimerBehavior with value of
> TIMEOUT, the onPostProcessTarget methods is being called immediately rather
> than it should wait for the
Hi,
straight away posting from readme here :)
https://github.com/vineetsemwal/quickview
QuickView is a wicket component(RepeatingView) ,it works with wicket
6.0.0-beta2 currently,it lets you adds new rows or remove the rows
without the need to re-render the whole repeater again when used with
aj
Hi,
We recently upgrade to Wicket 1.5. One of the major concern during that
migration was to deal with the new order of the header render strategy.
I see this is defined in AbstractHeaderRenderStrategy#get(), and reading
https://issues.apache.org/jira/browse/WICKET-4000 I understand the
reason