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

Martin Grigorov commented on WICKET-4545:
-----------------------------------------

The problem is in org.apache.wicket.markup.Markup#find(String) method which 
skips the body of the ComponentTag assigned to TransparentWebMarkupContainer.
#find() method looks for the child's markup only at one level depth but it 
should look one more lever deeper for TWMC. But since 
Component#onComponentTag() works with a copy of the real ComponentTag I see no 
way how to mark the ComponentTag as auto or to set it some other flag/userData 
which to be used when deciding whether to skip the children or not.

Anyone have ideas ?  
                
> MarkupNotFoundException for Fragment and TransparentWebMarkupContainer
> ----------------------------------------------------------------------
>
>                 Key: WICKET-4545
>                 URL: https://issues.apache.org/jira/browse/WICKET-4545
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.6
>            Reporter: Dirk Forchel
>         Attachments: quickstart.zip
>
>
> Create a base WebPage with a TransparentWebMarkupContainer to allow 
> subclasses register CSS classes on the body tag. Add a Fragment to one of 
> these subsclasses, the markup of the Fragment is not found. 
> See also 
> http://apache-wicket.1842946.n4.nabble.com/MarkupNotFoundException-for-Fragment-and-TransparentWebMarkupContainer-tp4619968.html
> Exception thrown:
> org.apache.wicket.markup.MarkupNotFoundException: No Markup found for 
> Fragment testFragment in providing markup container [Page class = 
> org.foo.HomePage, id = 0, render count = 1]
> at 
> org.apache.wicket.markup.html.panel.FragmentMarkupSourcingStrategy.getMarkup(FragmentMarkupSourcingStrategy.java:143)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to