[WICKET-5585] Wicket Extension Automplete does not work well with JavaScriptFilteredIntoFooterHeaderResponse

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.15.0
• Fix Version/s: 6.16.0, 7.0.0-M2
• Component/s: wicket-extensions
• Environment: Ubuntu Java 7
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Thibault Kruse
• Created: 07/May/14 18:33
• Updated: 07/Jul/14 08:08
• Resolved: 08/May/14 10:05

Description

When using JavaScriptFilteredIntoFooterHeaderResponse to render JS items at the bottom of the document body, this does not affect OnDomReadyHeaderItems. Wicket Extensions Autocomplete Textfield relies on such a OnDomReadyHeaderItem. As a consequence, when using both, the first item in the document HEAD calls Wicket.AutoComplete before the respective wicket js file has been loaded, breaking the Autocomplete Textfield.

Additionally JavaScriptFilteredIntoFooterHeaderResponse is final, so it cannot be trivially patched. our current workaround was to copy & paste JavaScriptFilteredIntoFooterHeaderResponse using a custom filter.

Not sure how best to fix this.

Issue Links

• relates to: WICKET-5612 If Wicket JS libs are moved to footer, AbstractAutoCompleteBehavior throws "Uncaught ReferenceError: Wicket is not defined"

Sub-Tasks

• Make JavaScriptFilteredIntoFooterHeaderResponse non-final to be able to create custom filters: Resolved