Have you tried to use the TransparentWebMarkupContainer? based on the
migration guide this could be a potential solution.
also have a look at this open bug
https://issues.apache.org/jira/browse/WICKET-3045
then after using the TransparentWebMarkupContainer... wicket was no
longer able to find some of the components in extended pages from my
parent page.
cheer gab
On 07/10/10 00:14, Alexander Morozov wrote:
Hi,
ParentPage.html:
<div wicket:id="wrapper">
<wicket:child/>
</div>
I know how it can be achieved in Wicket 1.4 (WebMarkupContainer with
overrided isTransparentResolver), but I cannot get the same behavior in case
of Wicket 1.5.
Wicket gurus, I need your advice :)
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
