feel free to open a jira issue attaching a quickstart that reproduces the problem.
-igor On Tue, Feb 9, 2010 at 12:37 AM, Andreas Lüdtke <sam.lued...@t-online.de> wrote: > Can someone please confirm if this is a bug? If yes, I will create a JIRA > issue if I'm allowed to do that. > > Thanks > > Andreas > >> -----Original Message----- >> From: Andreas Lüdtke [mailto:sam.lued...@t-online.de] >> Sent: Saturday, February 06, 2010 7:43 PM >> To: users@wicket.apache.org >> Subject: AbstractAjaxTimerBehavior#onTimer() doesn't work in >> deployment mode >> >> Hi, >> >> I'm using wicket 1.4.6 and saw that the onTimer method of an >> AbstractAjaxTimerBehavior object isn't called, when I switch >> vom development >> mode to deployment mode. This happens also with wicket 1.4.5. >> >> Is there something I need to do to get it working in deployment mode? >> >> In addition, after calling AbstractAjaxTimerBehavior.stop() >> the onTimer >> method is still called (of course only in development mode). ;-) >> >> If someone finds the time to fix this, I would be glad if >> this person could >> implement a restart() method to start the timer after it has >> been stopped. >> >> Andreas > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
