cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject Re: [WARNING] Compatibility warning
Date Sun, 14 Jul 2002 16:59:28 GMT
On Thu, 11 Jul 2002, Berin Loritsch wrote:

> The new pluggable pipelines are pretty cool, but the fact that they are
> now declared in <map:components/> is not backwards compatible!  In order
> to be able to reuse existing sitemaps, we must provide a reasonable
> default
> if that section is missing.

Or change the version number in the sitemap namespace when changes are
backward incompatible. Stefano suggested doing so for the flow extension
(which is going into 2.1 IIRC).

> A pipeline is not like a selector or actions in that we can live without
> them if our sitemap doesn't need them.  A pipeline is a central piece of
> Cocoon, and we must have a default.

Absolutely. I'd rather suggest the pipeline element does know of them
explicitely (know about those different pipeline implementations somehow)
rather than defining them in the sitemap. Should we be aware of a
infinite number of pipeline implementations? Those mentioned should be
enought, isn't it.

Giacomo


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


Mime
View raw message