Rainer Pruy wrote:
> Ooops, now I am a bit confused.
>
> - The initial request, was into the direction of aggregation.
> Thus I thought, the actual functionality missing is an aggregating generator
> (probably a more general one than is available with 2.1)
the initial request is about chaining two pipelines and not about
aggregation.
>
> - The xslt example, I considered just being a topic for general URLs that are
> capable of referring back to the pipeline engine
> (And probably this might not be available with Corona natively)
corona-pipeline doesn't support such a scenario, but corona-sitemap does
it the same way as Cocoon 2.x sitemaps by refering to servlet: URLs.
> Reinhard does your answer imply, such referring back should avoid
> serialization and just link to pipeline events passing
> (e.g. SAX or whatever is passed along a pipeline)?
>
> I would have considered this an internal optimisation for event streams that
> are compatible to the user/caller
> (XSLTTransformer in the current example)
>
> Did I get it wrong?
not sure ;-)
The XSLTTransformer sample is a bit confusing because in this case it is
the stylesheet that is created dynamically by a separate pipeline.
That's neither an aggregation nor a chaining scenario.
HTH
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member [EMAIL PROTECTED]
________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
