[ http://issues.apache.org/jira/browse/WICKET-131?page=comments#action_12460724 ] Juergen Donnerstag commented on WICKET-131: -------------------------------------------
I dont see how these things relate. wicket:fragment is not using auto-ids which is what InheritedMarkupMarkupLoader:441 handles. Do you have a junit test case? Juergen > wicket:fragment tag not handled properly when used with markup inheritance > -------------------------------------------------------------------------- > > Key: WICKET-131 > URL: http://issues.apache.org/jira/browse/WICKET-131 > Project: Wicket > Issue Type: Bug > Components: wicket > Affects Versions: 2.0 > Reporter: Igor Vaynberg > Assigned To: Juergen Donnerstag > Priority: Critical > Fix For: 2.0 > > > 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
