Christian Haul wrote: > > On 08.Oct.2002 -- 02:17 PM, Carsten Ziegeler wrote: > > Sylvain Wallez wrote: > > > > > > Good, we're in accordance again ;-) > > > > > Yup. > > > > > However, can you explain the exact purpose of > > > <map:component-configurations>, and how it is handled ? > > > > > > I see that it is now defined in the Processor interface, but can't > > > understand how it is used and what CocoonComponentManager exactly does > > > with it (this stack management is black magic). > > > > > > How is it related to <map:components> which is nothing more than the > > > configuration of a ComponentManager and can thus hold any component > > > declaration ? > > > > > Ok...this whole thing is a cool (FS-like) implementation of dynamically > > configured components....still there?... > > Carsten, could you explain in a few words how this differs from the > modeConf parameter in the InputModule interface and what makes it > better here? > First, it's a general approach which works for all components (at least those looked up using the ComponentManager - it does not work for selectors). It is currently used and it works. And it allows to configure components in the sitemap which are *not* declared there - the cocoon user does not notice that these are Avalon components.
And this is the general use case: But sometimes you want to give your component some information/configuration and want to extend this in your subsitemap. So if you use this component in the main sitemap it gets the configuration of the main sitemap. If you use the component in the subsitemap it gets the configuration of the main sitemap and the subsitemap. Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
