Is this also same as: https://issues.apache.org/jira/browse/WICKET-2636
? I whish this could be fixed for 1.4.9.1 ** Martin 2010/5/21 Chris Colman <chr...@stepaheadsoftware.com>: > Enclosures have to be one of the top ten awesome features of wicket as > they allow us to wrap the many optional components in our CMS. They're > awesome because the 'wrapping' is automatically ditched if the 'wrappee' > is not visible. > > I was just wondering if anyone was able to reproduce this issue with the > quickstart I provided. We are wanting to redeploy a major wicket powered > CMS with the latest version of wicket but this issue is holding us back > at wicket version 1.4.1 but we need fixes and features included in more > recent releases. > > https://issues.apache.org/jira/browse/WICKET-2882 > > I've downloaded the source code and tried debugging the problem myself > but my lack of understanding of how wicket works internally with regard > to the lifecycle, the chain of resolvers and the interactions with child > components that may or may not be present means I get 'stumped' (pardon > the wicket pun) pretty quickly :) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
