[ https://issues.apache.org/jira/browse/WICKET-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629490#action_12629490 ]
Stefan Fussenegger commented on WICKET-1188: -------------------------------------------- I have the exact same problem with Wicket 1.3.4. I stepped through the code and found out that Border.get(String path) doesn't consider a border's body container to be special. Therefore, this doesn't work: <!-- This is a non transparent border --> <span wicket:id="actionsBorder"> <wicket:enclosure child="newLink"> <div class="action"> <a wicket:id="newLink"><img wicket:id="newButton" /></a> </div> </wicket:enclosure> </span> while this does work: <!-- This is a non transparent border --> <span wicket:id="actionsBorder"> <wicket:enclosure child="_body:newLink"> <div class="action"> <a wicket:id="newLink"><img wicket:id="newButton" /></a> </div> </wicket:enclosure> </span> (My border has it's own child components, if this makes a difference) > <wicket:enclosure child="xxx"> bug when located as first level son of a non > transparent border > ----------------------------------------------------------------------------------------------- > > Key: WICKET-1188 > URL: https://issues.apache.org/jira/browse/WICKET-1188 > Project: Wicket > Issue Type: Bug > Components: wicket > Reporter: Antoine Angénieux > Assignee: Juergen Donnerstag > Fix For: 1.3.0-rc2 > > > I can't tell since extacly for which version this does not work, or if it's a > long time bug, but it does not work the current trunk (27 nov 2007). > Example markup : > <!-- This is a non transparent border --> > <span wicket:id="actionsBorder"> > <wicket:enclosure child="newLink"> > <div class="action"> > <a wicket:id="newLink"><img wicket:id="newButton" /></a> > </div> > </wicket:enclosure> > </span> > always throws a MarkupException during onComponentTagBody method of Enclosure > class. > It seems that the child lookup based on the 'child' parameter of the > Enclosure tag is erroneous : when it asks its parent to resolve the component > with childId, it only finds the Enclosure element, thus failing to locate the > child BELOW enclosure. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.