You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Pedro Santos (JIRA)" <ji...@apache.org> on 2016/08/18 02:08:20 UTC

[jira] [Assigned] (WICKET-6219) Fragment fails to report an error in development mode

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

Pedro Santos reassigned WICKET-6219:
------------------------------------

    Assignee: Pedro Santos

> Fragment fails to report an error in development mode
> -----------------------------------------------------
>
>                 Key: WICKET-6219
>                 URL: https://issues.apache.org/jira/browse/WICKET-6219
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.24.0
>            Reporter: Octavian Ciubotaru
>            Assignee: Pedro Santos
>         Attachments: fragmentbug.zip
>
>
> Fragment under certain circumstances fails to report errors while in development mode.
> In my case Fragment had the same id as markupId. Probably this should be allowed but in this case it triggers a bigger problem, it is silently ignored errors and even works in development, and fails in deployment mode.
> To trigger this bug, fragment must be inside a TransparentWebMarkupCotainer and <wicket:child>. If we leave out either TransparentWebMarkupCotainer or <wicket:child> it works, i.e. fails with correct message in either mode.
> Please check attached sample project that exhibits this behavior. Try an run it with a different configuration type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)