> to resolve the wicket:enclosure tag itself. > > the tag handler will assign a wicket:id to the wicket:enclosure tag. > the component resolver then has to resolve that wicket:id to a > component.
Ah, ok. At first it seemed strange to need an EnclosureResolver when wicket already knew that it was an Enclosure but now that you explain it as a two phase process: 1) handle tag to get a wicket:id 2) resolve the enclosure component i.e. look for a component with that wicket:id it now makes sense. > > -igor > > On Fri, Sep 18, 2009 at 8:35 PM, Chris Colman > <[email protected]> wrote: > >> to make the component a direct child of enclosure you would have to > >> have an Enclosure component that is explicitly added into the > >> hierarchy, at which point you can simply use a WebMarkupContainer > >> whose visibility is tied to that of the child to replicate the > >> functionality. the whole point of enclosure is that there is no > >> java-side component. > > > > Ok, well I'll drop that approach as an option. > > > > One thing I don't understand: > > > > [This question applies to any markup type/resolver pair I suppose] > > > > Is EnclosureResolver.resolve meant to be called to resolve the children > > of an Enclosure or to resolve the Enclosure itself? > > > > > > --------------------------------------------------------------------- > > 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]
