You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2015/10/16 15:32:06 UTC

[jira] [Resolved] (WICKET-6005) WicketRuntimeException from AjaxPagingNavigator#onAjaxEvent

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

Sven Meier resolved WICKET-6005.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 8.0.0-M1
                   7.1.0
                   6.21.0
                   1.5.14

You're right. Many thanks!

> WicketRuntimeException from AjaxPagingNavigator#onAjaxEvent
> -----------------------------------------------------------
>
>                 Key: WICKET-6005
>                 URL: https://issues.apache.org/jira/browse/WICKET-6005
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.13, 6.20.0, 7.0.0, 8.0.0-M1
>            Reporter: Sven Haster
>            Assignee: Sven Meier
>              Labels: ajax, navigator
>             Fix For: 1.5.14, 6.21.0, 7.1.0, 8.0.0-M1
>
>
> 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 {code}setOutputMarkupId(true){code} *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 {code}setOutputMarkupId(true){code}. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)