Hi, I haven't looked at your app but I think I know what is the problem. AccessDeniedPage will be shown if you try to use a disabled Behavior. I.e. your custom behavior schedules JavaScript timer (setTimeout) that will trigger after 2 secs, then you stop it, then the timer fires and at the server side Wicket realizes that the behavior is not enabled (stopped).
This problem is solved in Wicket 6. AbstractAjaxTimerBehavior is not restartable. Each time you call #stop() on it it will remove the timer (clearTimeout) at the client side too. Next time you (re-)start it it will schedule a completely new timer. On Thu, Oct 4, 2012 at 10:27 AM, Vignesh Palanisamy <[email protected]> wrote: > Hi every one > > AbstractAjaxRestartableTimerBehavior - "patched up" version of > AbstractAjaxTimerBehavior to provide "restart" functionality. > > we are using the AbstractAjaxRestartableTimerBehaviour it works fine in the > previous version right now we are upgrading wicket to 1.5.8 in that while > stopping the Auto Refresh timerBehavior shows the Access denied page > > i had attach an quick start program with it.. in that i set the duration as > 2 seconds. every 2 seconds it will update the feedback panel... click stop > link that error will appears.. > > > is there any other solution for it.. > > > thanks in advance > Vignesh Palanisamy > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
