You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Konstantin Iakimov (JIRA)" <ji...@apache.org> on 2013/03/01 07:05:14 UTC
[jira] [Commented] (WICKET-5060) Broken usage of fragment inside
AbstractColumn.populateItem
[ https://issues.apache.org/jira/browse/WICKET-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590270#comment-13590270 ]
Konstantin Iakimov commented on WICKET-5060:
--------------------------------------------
Problem is deeper than I think before - exception raised when fragment has same name as component on ancestor page.
Test sources attached, and may be it wasnt broken in 6.4 as I pointed in bug, may be the problem is older ...
> Broken usage of fragment inside AbstractColumn.populateItem
> -----------------------------------------------------------
>
> Key: WICKET-5060
> URL: https://issues.apache.org/jira/browse/WICKET-5060
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-extensions
> Affects Versions: 6.4.0
> Reporter: Konstantin Iakimov
>
> Page with DataTable, add new AbstractColumn with inlined populateItem.
> AbstractColumn.populateItem add fragment from same page with any kind of component(s) inside fragment.
> Exception
> The component(s) below failed to render. Possible reasons could be that: 1) you have added a component in code but forgot to reference it in the markup (thus the component will never be rendered), 2) if your components were added in a parent container then make sure the markup for the child container includes them in <wicket:extend> ... and list of component id's from fragment multiplied by amount of rows in DataTable
> With removing fragment and creating separate panel - exception gone and all works OK.
--
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