>Is this also same as: https://issues.apache.org/jira/browse/WICKET-2636 ?
It looks very similar though the conditions are slightly different. 2882 doesn't need to be in an 'extends' markup context to occur. I note this from the comments in 2636: "<wicket:component> - Creates a Wicket component on the fly." Which makes these bugs much more similar than they seem at first glance. They could in fact be caused by the same problem even though they are distinct bugs. 2882 is also related to components that are created on the fly - not using the wicket:component tag but using an IComponentResolver implementation which will also result in a component being created on the fly. There may be some fundamental lifecycle issue here that is a result of the way 'on the fly' components do not undergo the same 'ordering of the lifecycle processing' that 'pre instantiated' components do. It's a shame because the ability to create components on the fly, whether by wicket:component or using component resolvers is a majorly powerful feature of wicket that I haven't been able to find in most other frameworks. >I whish this could be fixed for 1.4.9.1 Ditto bro! I'm very keen to migrate from 1.4.1 up to the latest 1.9.x. > >** >Martin > >2010/5/21 Chris Colman <[email protected]>: >> 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: [email protected] >> For additional commands, e-mail: [email protected] >> >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
