[jira] [Updated] (WICKET-5440) TransparentWebMarkupContainer makes resolving of fragment markup fail on child pages

["Bertrand Guay-Paquet (JIRA)" <ji...@apache.org>]

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

Bertrand Guay-Paquet updated WICKET-5440:
-----------------------------------------

    Attachment: WICKET-5440.zip

Quickstart reproducing the issue.

Has child pages with and without a TransparentWebMarkupContainer on the parent page class.

> TransparentWebMarkupContainer makes resolving of fragment markup fail on child pages
> ------------------------------------------------------------------------------------
>
>                 Key: WICKET-5440
>                 URL: https://issues.apache.org/jira/browse/WICKET-5440
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 6.12.0
>            Reporter: Bertrand Guay-Paquet
>         Attachments: WICKET-5440.zip
>
>
> I wanted to do this kind of page layout:
> <div wicket:id="childContainer">
>   <wicket:child />
> </div>
> to add css classes to a child container in the parent page class. For this to work, I added a TransparentWebMarkupContainer with id "childContainer" to the parent page class. This works in some cases, but if the child page class defines wicket fragments, their markup is not found.
> When searching for the child's fragment's markup fragment, Markup.java (line 233) skips all the markup contained in the <body> tag because it has a wicket:id.
> Reference for the technique I used:
> http://stackoverflow.com/questions/5068142/can-a-wicketchild-tag-be-nested-under-another-component-on-the-page 



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)