Mailing-List: contact wicket-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: wicket-dev@incubator.apache.org
Message-ID: <1186836.1172785970712.JavaMail.jira@brutus>
Date: Thu, 1 Mar 2007 13:52:50 -0800 (PST)
From: "Xavier Hanin (JIRA)" <jira@apache.org>
To: wicket-commits@incubator.apache.org
Subject: [jira] Reopened: (WICKET-343) AbstractAjaxTimerBehavior only
 trigger one request
In-Reply-To: <6709501.1172780810909.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/WICKET-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Hanin reopened WICKET-343:
---------------------------------


I think there is still a problem with the latest code: the contribution of the javascript only occurs if renderHead is called, and this is only the case if the component to which the AbstractAjaxTimerBehavior is attached. So if for example you only call appendJavascript to your AjaxRequestTarget, it won't occur, and you will have only one request.

> AbstractAjaxTimerBehavior only trigger one request
> --------------------------------------------------
>
>                 Key: WICKET-343
>                 URL: https://issues.apache.org/jira/browse/WICKET-343
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3
>         Environment: Firefox 2.0.0.2
>            Reporter: Xavier Hanin
>         Assigned To: Johan Compagner
>             Fix For: 1.3
>
>
> AbstractAjaxTimerBehavior only triggers one request and then stop. The clock example in wicket-examples show the problem. Reverting to revision 511893 fixes the problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.