[
https://issues.apache.org/jira/browse/WICKET-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474945#comment-13474945
]
Sebastian Gooren commented on WICKET-4545:
------------------------------------------
In the meantime, this can be fixed by using the TransparentWebMarkupContainer
as the markupProvider constructor argument.
Cloning the markup stream or marking the TWMC as an auto component seems
overkill or abusing the auto flag, no?
On the other end the wicket internals have become so much cleaner since 1.5
that an "if (component instanceof IComponentResolver) look_deeper" is out of
the question?
> MarkupNotFoundException for Fragment and TransparentWebMarkupContainer
> ----------------------------------------------------------------------
>
> Key: WICKET-4545
> URL: https://issues.apache.org/jira/browse/WICKET-4545
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.6
> Reporter: Dirk Forchel
> Attachments: quickstart.zip
>
>
> Create a base WebPage with a TransparentWebMarkupContainer to allow
> subclasses register CSS classes on the body tag. Add a Fragment to one of
> these subsclasses, the markup of the Fragment is not found.
> See also
> http://apache-wicket.1842946.n4.nabble.com/MarkupNotFoundException-for-Fragment-and-TransparentWebMarkupContainer-tp4619968.html
> Exception thrown:
> org.apache.wicket.markup.MarkupNotFoundException: No Markup found for
> Fragment testFragment in providing markup container [Page class =
> org.foo.HomePage, id = 0, render count = 1]
> at
> org.apache.wicket.markup.html.panel.FragmentMarkupSourcingStrategy.getMarkup(FragmentMarkupSourcingStrategy.java:143)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
