[WICKET-6005] WicketRuntimeException from AjaxPagingNavigator#onAjaxEvent

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.13, 6.20.0, 7.0.0, 8.0.0-M1
• Fix Version/s: 1.5.14, 6.21.0, 7.1.0, 8.0.0-M1
• Component/s: wicket
• Labels: ajax navigator
• Assignee: Sven Meier
• Reporter: Sven Haster
• Created: 16/Oct/15 12:33
• Updated: 16/Oct/15 13:31
• Resolved: 16/Oct/15 13:31

Description

In WICKET-5974 a change was added where the AjaxPagingNavigator checks if its pageable has a parent that is a) not a repeater and b) has outputMarkupId set to true. If not, a WicketRuntimeException is thrown ("Unable to find a parent component that is no repeater and has setOutputMarkupId(true)")

This is a significant break from the logic before, where the AjaxPagingNavigator checked if its pageable has a parent that is not a repeater and if so, added it to the AjaxRequestTarget, which then would check if the component has

setOutputMarkupId(true)

or if it is a page. (see AjaxRequestHandler#add(Component...) )

This last part is significant because it means that any repeater added directly to a page before would work with the AjaxPagingNavigator but now it will only work if that page has

setOutputMarkupId(true)

.

Issue Links

• is broken by: WICKET-5974 Change AjaxPagingNavigator#onAjaxEvent() to only consider parent components that have setOutputMarkupId(true)