[
https://issues.apache.org/jira/browse/WICKET-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794117#action_12794117
]
Juergen Donnerstag commented on WICKET-2636:
--------------------------------------------
As side note: copied from http://cwiki.apache.org/WICKET/wickets-xhtml-tags.html
<wicket:component> - Creates a Wicket component on the fly. Needs a class
attribute. Though this has been in wicket for a long time, it is still kind of
an unsupported feature, as most of the core developers believe that this may
lead to misuse of the framework. Before heavily relying on this feature, you
might want to contact the user list to discuss alternative strategies. (THIS
TAG IS NOT SUPPORTED BY THE CORE TEAM)
See WICKET-2541 for a similar problem. Since the solution is so simple, we'll
rather strive for a small and easy to maintain Enclosure implementation, than
adding lots of (complicated) magic for it to work in every circumstance. But of
course is just my opinion
> 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.
