[
https://issues.apache.org/jira/browse/WICKET-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053726#comment-13053726
]
Juergen Donnerstag commented on WICKET-3829:
--------------------------------------------
The problem is that "form" is the container containing the fragment markup and
not the panel.
public TestFragment(String id) {
super(id, "fragment", form /* ChildPanel.this */);
In 1.4 we did more searching for the fragment markup and even allowed to not
provide a "provider" component or have the fragment outside <wicket:panel>
etc.. With the introduction of MarkupFragment and getMarkup() we did not
re-implement that magic. The idea is to make the code more readible because
from looking at the source code you now exactly now where to find the fragment
markup. The logic is in FragmentMarkupSourcingStrategy which is pluggable and
can be enhanced if you want to.
> No Markup found for Fragment
> ----------------------------
>
> Key: WICKET-3829
> URL: https://issues.apache.org/jira/browse/WICKET-3829
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC4
> Reporter: Pedro Santos
> Assignee: Juergen Donnerstag
> Attachments: WICKET-3829-1.5.zip, reference.zip
>
>
> The bug happens while using an fragment in a child panel whose parent
> declared the wicket:child tag inside some WebMarkupContainer. This used to
> work in 1.4, I'm attaching 2 quick stars, the reference in 1.4 and another
> reproducing the problem in 1.5
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
