You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2006/12/02 20:45:23 UTC
[jira] Assigned: (WICKET-131) wicket:fragment tag not handled
properly when used with markup inheritance
[ http://issues.apache.org/jira/browse/WICKET-131?page=all ]
Juergen Donnerstag reassigned WICKET-131:
-----------------------------------------
Assignee: Juergen Donnerstag (was: Juergen Donnerstag)
> 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