[
https://issues.apache.org/jira/browse/WICKET-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479458
]
Ryan Crumley commented on WICKET-305:
-------------------------------------
This continues to be a problem with our application on 1.2.5 with repeaters,
loops, and dataviews. Not only does it effect ajax but any other
javascript/header contributions. If 1.3 is not going to be released VERY soon
this should be a much higher priority issue (IMHO).
> Wicket 1.2.5 is not adding header contributions correctly after serving an
> ajax request
> ---------------------------------------------------------------------------------------
>
> Key: WICKET-305
> URL: https://issues.apache.org/jira/browse/WICKET-305
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.2.5
> Environment: quickstart, jdk 1.5
> Reporter: Ryan Crumley
> Attachments: ajaxbug-wicket1.2.5.tar.gz
>
>
> Execute the attached quickstart application for reproduction steps.
> The bug involves a loop which contains an ajax link that adds its parent
> container to the target. After the request the thread has not been cleaned up
> and the next request to that thread will not serve any header contributions
> that were served during the previous request.
> I _HAVE_ verified that the code works fine if you remove the Loop that wraps
> the ajax link.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
