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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427677#comment-15427677 ] 

ASF subversion and git services commented on WICKET-6219:
---------------------------------------------------------

Commit 381391bc2d4ae7567a385987152687453c213121 in wicket's branch refs/heads/wicket-6.x from Pedro Henrique Oliveira dos Santos
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=381391b ]

WICKET-6219 testing the tag name to prevent conflict when resolving fragments and components markup


> 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)