[WICKET-4545] MarkupNotFoundException for Fragment and TransparentWebMarkupContainer

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.6
• Fix Version/s: 6.16.0, 7.0.0-M2
• Component/s: wicket
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Dirk Forchel
• Created: 09/May/12 11:35
• Updated: 27/May/14 07:47
• Resolved: 27/May/14 07:47

Description

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)

Issue Links

• is duplicated by: WICKET-4654 FragmentMarkupSourcingStrategy doesn't see fragment markup which is declared in subclassed panel.
• is duplicated by: WICKET-5440 TransparentWebMarkupContainer makes resolving of fragment markup fail on child pages
• relates to: WICKET-5580 Allow markup to find child fragments when wicket:child is inside a component tag