Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ap-cocoon-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: dev@cocoon.apache.org
From: BURGHARD =?ISO-8859-15?Q?=C9ric?= <eric.burghard@systheo.com>
Subject: Re: Suggestion for XHTMLSerializer
Date: Sun, 07 Aug 2005 23:50:41 +0200
Lines: 33
Message-ID: <dd5vl1$1ba$1@sea.gmane.org>
References: <b677085305080202252fb491ff@mail.gmail.com>
 <42F5E165.1090700@gmx.de> <dd502d$gn0$1@sea.gmane.org>
 <200508080115.54273.niclas@hedhman.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
User-Agent: KNode/0.9.1
Sender: news <news@sea.gmane.org>

> Why not collapse the entire pipeline into a single component as well, that
> would eliminate a massive amount of bugs and testing time of the Sitemap
> ;o)
>

It's a brillant idea, but it's yours :-D

> Componentization with semantically well-defined contracts in between, is a
> far better than large monoliths with innumerous permutations of

And who is talking about large monoliths now ;-) ?

> configuration, rules/exceptions, outcomes, side-effects and associated
> subtleties. Do one thing, and do it damn well. That is what we like about
> Cocoon... Adult Lego!
>

That's what i like in cocoon too.

> Virtualization of a pack of transformers, with optional Generator and
> Serializer seems like doing the job more elegantly. At least as much as I
> have understood reading this all.
>

I use virtual generator with an xmldb generator and some bunch of
transformers on my project to simplify some common pipelines. I found that
effectively usefull and elegant, but xslserialisation is not directly
related to virtualisation, even if you could stack (i know that you will
appreciate that as a componentizator :-) some transformers with an
xslserializer.

Regards