[
https://issues.apache.org/jira/browse/WICKET-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073955#comment-16073955
]
Andrea Del Bene commented on WICKET-6415:
-----------------------------------------
hi [~kbachl]
Wicket 8 is stricter about component hierarchy consistency, that's why you get
the exception. Please note that even with Wicket 7 you get the following
warning message:
bq. WARN org.apache.wicket.page.XmlPartialPageUpdate - Component '[Component
id = history]' with markupid: 'history3' not rendered because it was already
removed from page
if you invoke "form.addOrReplace(component);" before "target.add(component);"
in both the handlers you will avoid the exception with Wicket 8
> new Components added in AjaxRequest break with no Page found error
> ------------------------------------------------------------------
>
> Key: WICKET-6415
> URL: https://issues.apache.org/jira/browse/WICKET-6415
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 8.0.0-M1, 8.0.0-M2, 8.0.0-M3, 8.0.0-M4, 8.0.0-M5,
> 8.0.0-M6, 8.0.0-M7
> Environment: any
> Reporter: Korbinian Bachl
> Priority: Critical
> Attachments: ajaxErrorDemo.tar.gz
>
>
> run attached quickstart-project (code behind works well in wicket 7 and
> lower), enter anything into the ajaxfield to trigger the updatebehaviour and
> you get error:
> Unexpected RuntimeException
> Last cause: No Page found for component [Component id = history]
> Stacktrace
> Root cause:
> org.apache.wicket.WicketRuntimeException: No Page found for component
> [Component id = history]
> at org.apache.wicket.Component.getPage(Component.java:1755)
> at
> org.apache.wicket.ajax.AjaxRequestHandler.add(AjaxRequestHandler.java:231)
> at
> com.mycompany.demo.tile.AjaxDemoPanel$2.onUpdate(AjaxDemoPanel.java:118)
> at
> org.apache.wicket.ajax.form.AjaxFormComponentUpdatingBehavior.onEvent(AjaxFormComponentUpdatingBehavior.java:156)
> at
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:151)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)