cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ken Barozzi" <nicola...@apache.org>
Subject Re: [Vote]: Where to define the sitemap components?
Date Thu, 14 Mar 2002 10:51:25 GMT
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>

> 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.

I personally think it's not so confusing, but I understand the point.

> b) Having said a), if we decide for the xconf, it will *not* be possible
>    to define custom components in sub-sitemaps!

Ugh. Not nice. I would be -1 on this! We need some sub declaration system.

> 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...

Not  ;-)

As always, needs never collide, only implementations do. (should I change
signature on this? ;-)
So by implementing the configuration in only sitemap.xmap or cocoon.xconf we
break some needs.

What was the need to put components in cocoon.xconf?
IIRC, it was to reduce clutter in sitemap.xmap, originally.
When the new layout of the samples is committed, there won't be much there
in every sitemap.
So this issue could be resolved, and components be declared in sitemaps.

But think of upgrade. If I upgrade some components, I need to change every
definition in every sitemap where it's declared. Not good.
But this will be resolved AFAIK with the next-to-be-defined Blocks.

So I'm +1 for taking the components away from xconf, and placing them only
in the sitemap for the time being.
This SOC issue will be resolved with Blocks.
If someone really wants to separate this in two files, he can always include
the components as external entities (XML), but I wouldn't recommend it (and
Stefano would skin me ;-).

Could this be ok?

--
Nicola Ken Barozzi                   nicolaken@apache.org
            - verba volant, scripta manent -
   (discussions get forgotten, just code remains)
---------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message