You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Eelco Hillenius (JIRA)" <ji...@apache.org> on 2007/03/11 07:27:09 UTC

[jira] Resolved: (WICKET-276) AbstractHeaderContributor.cleanup() will never be called

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

Eelco Hillenius resolved WICKET-276.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.6

This issue seems to have been fixed already. Just checked it with 1.2.6 and cleanup is called properly

> AbstractHeaderContributor.cleanup() will never be called
> --------------------------------------------------------
>
>                 Key: WICKET-276
>                 URL: https://issues.apache.org/jira/browse/WICKET-276
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.4
>         Environment: winstone servlet engine
>            Reporter: andre kullmann
>             Fix For: 1.2.6
>
>
> I am using the HeaderContributor.forJavaScript method. and the HeaderContributor.cleanup() is never called. so processedEntries will be stay alive in thead and if the thread will be reused for another request the renderHead method will not process the contributors which are known in the thead form previouse request. after i add a new HeaderContributor().cleanup(); in WebRequestCycle.onEndRequest()  every thing works fine.

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