[
https://issues.apache.org/jira/browse/WICKET-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
selckin updated WICKET-3725:
----------------------------
Description:
The attached quick start, fails to render the components inside the fragment,
because it will pick the <span wicket:id="text"> instead of the fragment as
markup.
I believe the id are only required to be unique "per level", so this should
work and it should properly find the <wicket:fragment wicket:id="text">.
This also worked fine in 1.4
was:
The attached quick start, fails to render the components inside the fragment,
but only if the other fragment is inside the .html, if you comment it out, it
will start working.
Having unused fragments in the html worked fine in 1.4 (if that's the reason?)
Summary: wickettag contents aren't skipped when trying to find markup
in 1.5 (was: unused fragments seem to cause invalid fragment markup resolution
in 1.5)
> wickettag contents aren't skipped when trying to find markup in 1.5
> -------------------------------------------------------------------
>
> Key: WICKET-3725
> URL: https://issues.apache.org/jira/browse/WICKET-3725
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC4
> Reporter: selckin
> Assignee: Juergen Donnerstag
> Attachments: fragment-bug.rar, fragment-skipping.patch
>
>
> The attached quick start, fails to render the components inside the fragment,
> because it will pick the <span wicket:id="text"> instead of the fragment as
> markup.
> I believe the id are only required to be unique "per level", so this should
> work and it should properly find the <wicket:fragment wicket:id="text">.
> This also worked fine in 1.4
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
