Carlos Tejo Alonso wrote:
> Hello,
>
> I would like to do that:
>
> input_1 -> transformation_2 -> output_1
> input_2 -> transformation_2 -> output_2
>
> output_1 + ouput_2 -> transformation -> output_1+2
>
> What's the way to connect 2 pipelines in corona-pipeline?
Currently nested pipelines
well, can i wish support of dynamic XSLT generation in addition?
stage1 - xml1 -> xslt1 -> xslt2
stage2 - xml2 -> xslt2 -> result-xml
as simplest example - Schematron rules
with best wishes,
Slav
On Fri, Aug 15, 2008 at 6:04 PM, Reinhard Pötz <[EMAIL PROTECTED]> wrote:
> Carlos Tejo Alonso wrot
18 August 2008 07:41
To: users@cocoon.apache.org
Subject: Re: [cocoon3] Nested pipelines
well, can i wish support of dynamic XSLT generation in addition?
stage1 - xml1 -> xslt1 -> xslt2
stage2 - xml2 -> xslt2 -> result-xml
as simplest example - Schematron rules
with best wishes,
Slav
On Fri, Aug
Vyacheslav Sedov wrote:
> well, can i wish support of dynamic XSLT generation in addition?
>
> stage1 - xml1 -> xslt1 -> xslt2
> stage2 - xml2 -> xslt2 -> result-xml
The simplest way would be extending the XSLTTransformer class to also
accept an InputStream for the XSLT file (currently it only su
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 xslt example, I considered just being a topic for general U
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 chainin
