[
https://issues.apache.org/jira/browse/WICKET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507939
]
Juergen Donnerstag commented on WICKET-592:
-------------------------------------------
Development is currently focussed on 1.3 and to get 1.3 out soon. Which is why
we are only fixing realy critical bugs in 1.2.x. I understand that a
workaround is available for 1.2.6 which is why I lean towards not fixig it in
1.2.6. In case you can live with that, I'd appreciate you closing the entry.
Thanks.
Juergen
> A fragment will not be found when it is nested, e.g., in a border
> -----------------------------------------------------------------
>
> Key: WICKET-592
> URL: https://issues.apache.org/jira/browse/WICKET-592
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.2.6
> Reporter: Thomas Singer
> Assignee: Juergen Donnerstag
> Fix For: 1.3.0-rc1
>
> Attachments: src.zip
>
>
> sketched markup:
> <div wicket:id="myBorder">
> ...
> <wicket:fragment wicket:id="fragmentSource">...</wicket:fragment>
> ...
> <tr wicket:id="fragmentTarget">...</tr>
> </div>
> Following components were added to the page:
> MyBorder border = new MyBorder("myBorder");
> border.add(new Fragment("fragmentTarget", "fragmentSource"));
> this.add(border);
> It always cannot find the "fragmentSource". After debugging the Fragment's
> renderFragment() method, I guess it is caused by the method call
> providerMarkupStream.findComponentIndex(null, markupId), because the
> componentMap in Markup contains no "fragmentSource", but only
> "myBorder:fragmentSource".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
