On Fri, Oct 11, 2002 at 11:49:50AM +0200, Christian Haul wrote: > On 10.Oct.2002 -- 11:50 PM, Stefano Mazzocchi wrote: ... > > why aren't you declaring them in the sitemap? > > Because they are not only relevant to the sitemap and declaration of > general components in the sitemap was considered bad. > > > > Take a look at this > > > > <map:sitemap> > > <map:components> > > ... > > <map:expanders> > > <map:expander name="A" src="..."/> > > <map:expander name="B" src="..."/> > > </map:expanders> > > ... > > </map:components> .... [snip naming debate] [snip (unneeded) expander-sets] > > isn't it more precisely describing what you want to achieve? > > No. It changes a name and not for the better and places the > declaration to a place were SoC is breached. What really is needed is > multiple xconfs. Most (all?) sitemap components should be in a local > xconf.
How would multiple configs help? I'd imagine: cocoon.xconf -> declare and configure generic components sitemap.xconf -> declare and configure sitemap components (map:components stuff) sitemap.xmap -> use components But even then, input modules would belong in cocoon.xconf (being generic), so multiple configs isn't the answer to the problem. > Until then, it should stay in the one that we have. How about if they could be declared in either cocoon.xconf (when used generically) or sitemap.xmap (when used as 'expanders')? Two different 'contexts', two different configuration syntaxes. > It probably doesn't add anything to this discussion, but maybe this > illustrates some aspects. > http://xml.apache.org/cocoon/userdocs/concepts/modules.html > > BTW did someone notice, that these thingies that we spend so much time > about now are in CVS since Q1 02?? :) Probably because no-one had any clue they were _useful_. Their general usefulness was so well camouflaged by docs like the one above. --Jeff > Chris. > -- > C h r i s t i a n H a u l > [EMAIL PROTECTED] > fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
