[WICKET-188] Header contribution is sometimes not rendered after the request

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.3, 1.2.4
• Fix Version/s: 2.0 branch (discontinued), 1.2.5, 1.3.0-beta1
• Component/s: wicket
• Environment: Tomcat 5.5.20, jdk 1.5.0_09, wicket 1.2.4
• Assignee: Igor Vaynberg
• Reporter: Robert Novotny
• Created: 29/Dec/06 12:06
• Updated: 01/Feb/07 06:34
• Resolved: 29/Dec/06 17:57

Description

The header contributions seem to be appearing and disappearing randomly. Let us have a simple webpage containing a link and a StringContributor. If I click on the link, the page refreshes and contributions appear normally. However, in the subsequent refreshes of that page in the browser (using the browser's refresh button) the contributions are not appearing.

There was already some fix in the HeaderContribution issue in Wicket 1.2.3. Does this problem have something in common with the fixed HeaderContribution issue in the Wicket 1.2.3? This problem does not occur with Wicket 1.2.1.

After a little bit of debugging, I am suspecting that the ,,entries" Set in the AbstractHeaderContributor is not properly cleaned up between the requests.

I have tried to blindly patch the AbstractBehavior according to the latest version in the trunk (there is some additional cleanup in this latest version) and this seems to have solved the problem (however I am not sure, whether this is sufficient).

Issue Links

• is related to: WICKET-68 header contribution is not rendered anymore after the first render