[
https://issues.apache.org/jira/browse/WICKET-6582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597127#comment-16597127
]
Jezza commented on WICKET-6582:
-------------------------------
Ok, so as I was creating the quickstart, I discovered the issue.
The issue wasn't that we didn't have a parent, the issue was that it was added
AFTER we added it to the target.
{code:java}
if (handler != null) {
Wicket.insert(handler, dialog, dialogContainer);
}
dialogRepeater.add(dialog);
{code}
We were adding it to the repeater after inserting it into the target in
Wicket#insert.
So, we just needed to move that line of code above the insert.
Feel free to close the ticket.
> Ajax should prevent components on a different page from rendering on the
> current one.
> -------------------------------------------------------------------------------------
>
> Key: WICKET-6582
> URL: https://issues.apache.org/jira/browse/WICKET-6582
> Project: Wicket
> Issue Type: Improvement
> Reporter: Jezza
> Priority: Major
>
> Heyo, we've just updated to Wicket 8, and run head first into WICKET-6140.
> The problem is that we use this behaviour to generate components without a
> page, and then render them into place using ajax.
> I think a better solution would be to only verify the page iff the component
> is on a page.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
