[
https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917297#action_12917297
]
Martin Grigorov commented on WICKET-3079:
-----------------------------------------
Juergen, you closed it as "Fixed" for 1.5-M3 but I didn't see any commits
related to this. Is it possible that your svn client failed to commit it
without you notice it?
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M3
>
> Attachments: fragments_test.rar, fragments_test.tgz
>
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also,
> FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is
> specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that
> if a fragment's markup is defined inside another fragment this exception is
> thrown. The problem occurs because the Fragment.getMarkup(final Component
> child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
