You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2010/08/27 08:07:53 UTC

[jira] Resolved: (WICKET-1563) renderOnLoadJavascript being called multiple times

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

Igor Vaynberg resolved WICKET-1563.
-----------------------------------

      Assignee: Igor Vaynberg  (was: Matej Knopp)
    Resolution: Incomplete

please provide a quickstart

> renderOnLoadJavascript being called multiple times
> --------------------------------------------------
>
>                 Key: WICKET-1563
>                 URL: https://issues.apache.org/jira/browse/WICKET-1563
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.3
>            Reporter: Carlos Pita
>            Assignee: Igor Vaynberg
>
> There are at least of couple of common scenarios where this happens:
>  - you add the component that is a header contributor to an ajax target: renderHead is called as part of target.respond() and latter by page.detach()
>  - you add the component that is a header contributor more than once to an ajax target. Normally you can't control this, because the component in question is added by another component indirectly, by adding some of its ancestors. renderHead is called multiple times as part of target.respond() and latter yet another time by page.detach()
> I think there must be a check to avoid repetitions of these nature, maybe by means of an id, the same as renderJavascript() does.

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