[
https://issues.apache.org/jira/browse/WICKET-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482141
]
Nick Johnson commented on WICKET-404:
-------------------------------------
That works for the simple testcase, but as soon as Fragments become involved,
it doesn't seem to help.
I'll attach another testcase showing the slightly more complex case. The
message in this case is:
WicketMessage: Markup does not contain a fragment with id=fragment1; Component:
[MarkupContainer [Component id = frag, page = net.spatula.testcase.ChildPage,
path = 3:frag.Fragment, isVisible = true, isVersioned = true]]
> Using Borders with Markup Inheritance causes component resolution failures
> --------------------------------------------------------------------------
>
> Key: WICKET-404
> URL: https://issues.apache.org/jira/browse/WICKET-404
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.2.5
> Reporter: Nick Johnson
> Attachments: testcase.jar
>
>
> If a Border is used by the BasePage in a markup inheritance implementation,
> Wicket is unable to resolve any of the components in the child page.
> I will attach a simple testcase for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
