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.
-igor On Fri, Sep 18, 2009 at 8:35 PM, Chris Colman <chr...@stepaheadsoftware.com> 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: 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
