> > >> as far as i rememember there is a collection registered in > setttings > > >> and then each component can also implement a resolver. > > >> > > >> the contract can be seen in markupcontainer#rendernext method > > >> 1) first walk over the component hierarchy and check if any are > > resolvers > > >> 2) walk over collection of resolvers in the settings > > >> > > >> as soon as true is returned from resolve iteration is stopped. > > What method should I override in Enclosure to invoke the above process? > > It would have to be a method that gets called prior to Enclosure calling > getChildComponent() which it does from onComponentBodyTag... does that > represent a staging problem?
I've tried many different combinations over a frustrating 3 days now in an attempt to get enclosure to fire off a 'resolve' on its children like most other parent components do. I'm beginning to wonder if what I'm doing is actually possible in wicket. Perhaps the retrieval of the dependent child component is happening to early in the lifecycle i.e. before the resolve has had a chance to instantiate and populate the children in the parent. Any ideas on the relative chance of success of this endeavour? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
