Re: AjaxSelfUpdatingTimerBehavior Once

2009-03-20 Thread Heidi Burn
Thank you very much, Kevin May I ask why isTemporary is not working? Heidi On Thu, Mar 19, 2009 at 11:10 PM, Kevin Logue ke...@viableoptions.ie wrote: If you just want to stop AjaxSelfUpdatingTimerBehavior after a particular event(or one call even), you could always call the stop method on the

Re: AjaxSelfUpdatingTimerBehavior Once

2009-03-20 Thread Igor Vaynberg
because if you do not stop the behavior it will generate a callback on the client for itself, but when istemporary() is true after it generated the callback it will be removed. so now the callback points to something that is not there. it should be ok to use istemporary() but you also have to call

AjaxSelfUpdatingTimerBehavior Once

2009-03-19 Thread Heidi Burn
Hi, guys, I code AjaxSelfUpdatingTimerBehavior with isTemporary() {return true;}. After being called once I get ERROR - RequestCycle   - java.lang.NullPointerException     at org.apache.wicket.request.

Re: AjaxSelfUpdatingTimerBehavior Once

2009-03-19 Thread Kevin Logue
If you just want to stop AjaxSelfUpdatingTimerBehavior after a particular event(or one call even), you could always call the stop method on the AjaxSelfUpdatingTimerBehavior. No idea if this is the best practice but it's worked for me. Kevin Heidi Burn wrote: Hi, guys, I code