[WICKET-131] wicket:fragment tag not handled properly when used with markup inheritance

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0 branch (discontinued)
• Fix Version/s: 2.0 branch (discontinued)
• Component/s: wicket
• Assignee: Juegen Donnerstag
• Reporter: Igor Vaynberg
• Created: 30/Nov/06 22:29
• Updated: 25/Dec/06 23:53
• Resolved: 25/Dec/06 23:53

Description

there is a problem when handling wicket:fragment tags that are defined within wicket:extend tags.

the problem is in InheritedMarkupMarkupLoader:441

what happens is that first WicketTagIdentified properly assigns tag.id to be the wicket:id defined within the fragment tag
but then the InheritedMarkupMarkupLoader visits the fragment and resets its tag.id to an autogenerated id

when rendering occurs markupfragment cannot find the markup of the fragment because its tag.id has been changed