Ok, this seems to be a very difficult task then. Let me state the following: a) There shouldn't be two places where one can define the sitemap components, so it's rather the xconf or the sitemap. But having both is absolutly confusing. b) Having said a), if we decide for the xconf, it will *not* be possible to define custom components in sub-sitemaps! c) If we opt for defining the components in the sitemap (as it is now) we help the sitemap editor in writing the pipelines as he can simply see which components are available.
So, SoC or not, is the above really what we want? I think, no! Hmm, currently I'm thinking of voting -1 for defining the components in the xconf. This would create a deadlock. Very interesting and funny thing... Carsten > Carsten Ziegeler wrote: > > Hi Team, > > I'm still not convinced that it is a good idea to have some components > (generators, transformers etc) of the sitemap defined in the cocoon.xconf > and some in the map:components section of the sitemap. > > We will confuse many users with this, believe me. There will be many > complains that for example the file generator isn't available any > more, as it is not visible in the sitemap. > > So for a forthcoming release, I propose to move them back into the > sitemap and after the release we can think of a better way of defining > components. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
