You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Richard Wilkinson (JIRA)" <ji...@apache.org> on 2009/12/23 17:24:34 UTC

[jira] Updated: (WICKET-2636) Wicket enclosure cannot find wicket container children when hidden and in an extended page

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

Richard Wilkinson updated WICKET-2636:
--------------------------------------

    Attachment: enclosure-component.zip

Quickstart attached which shows the bug

> Wicket enclosure cannot find wicket container children when hidden and in an extended page
> ------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2636
>                 URL: https://issues.apache.org/jira/browse/WICKET-2636
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.4.2, 1.4.3, 1.4.4, 1.4.5
>         Environment: Java 6, Linux 64bit
>            Reporter: Richard Wilkinson
>         Attachments: enclosure-component.zip
>
>
> When you have a wicket:enclosure, which is in a page which extends markup of another page, then it cannot find wicket:container components which are inside it, when it is hidden.
>     	<wicket:extend>
> 	    	<wicket:enclosure child="child">
> 	    		<div wicket:id="div"></div>
> 	    		<wicket:container wicket:id="container"></wicket:container>
> 	    		<div wicket:id="child"></div>
> 	    	</wicket:enclosure>
>     	</wicket:extend>
> It gives the normal wicket component not found exception, that you get when you don't reference the wicket:id in markup.
> Change the wicket:container to a div (or other html element) and it works correctly.
> Works on 1.4.1, 1.4.2 gives a different error, 1.4.3-1.4.5 give the error described here.
> It only seems to happen if the page extends markup, if you place it into a page which does not extend markup it works.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.