On 7/11/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
please make a jira issue for this yes, i guess we need some check on an id so that we dont add it twice
Done: https://issues.apache.org/jira/browse/WICKET-745 Xavier On 7/11/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
> Hi, > > I think I've found a bug in AbstractAjaxTimerBehavior... The problem happens > when a component to which an AbstractAjaxTimerBehavior is attached is > rendered by an AjaxRequestTarget which is not due to the timer, but to > another Ajax call. In this case it seems that the renderHead method called > on AbstractAjaxTimerBehavior adds another setTimeout() javascript call than > the one originally rendered, which makes the timer call happen twice as > frequently as it should. I haven't isolated the problem in a simple example, > so my analysis may be wrong (I'm experiencing this issue when working on > wicketstuff-push, so the source can be something else). > > Do you think my analysis make sense? Should I open an issue in JIRA? > > Xavier > -- > Xavier Hanin - Independent Java Consultant > http://xhab.blogspot.com/ > http://incubator.apache.org/ivy/ > http://www.xoocode.org/ >
-- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
