You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2013/11/07 09:51:25 UTC

[jira] [Resolved] (WICKET-5060) Fragment and Component with same id fail with misleading exception

     [ https://issues.apache.org/jira/browse/WICKET-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sven Meier resolved WICKET-5060.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 6.12.0
                   7.0.0

FragmentMarkupSourcingStrategy fails early now if fragment markup is no fragment tag

> Fragment and Component with same id fail with misleading exception
> ------------------------------------------------------------------
>
>                 Key: WICKET-5060
>                 URL: https://issues.apache.org/jira/browse/WICKET-5060
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket, wicket-extensions
>    Affects Versions: 6.4.0, 7.0.0
>            Reporter: Konstantin Iakimov
>            Assignee: Sven Meier
>            Priority: Minor
>             Fix For: 7.0.0, 6.12.0
>
>         Attachments: wicket-fragment-test.7z
>
>
> A page having a component from inherited markup *and* fragment with the *same* id fails with misleading exception message.
> Exception message:
> The component(s) below failed to render. Possible reasons could be that: 1) you have added a component in code but forgot to reference it in the markup (thus the component will never be rendered), 2) if your components were added in a parent container then make sure the markup for the child container includes them in <wicket:extend> ... and list of component id's from fragment multiplied by amount of rows in DataTable
> Cause: The markup of the component is used by the fragment.



--
This message was sent by Atlassian JIRA
(v6.1#6144)