Return-Path: <stefano@apache.org>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 21830 invoked from network); 19 Sep 2000 23:01:28 -0000
Received: from pop.systemy.it (194.20.140.28)
  by locus.apache.org with SMTP; 19 Sep 2000 23:01:28 -0000
Received: from apache.org (pv31-pri.systemy.it [194.21.255.31]) by
 pop.systemy.it (8.8.8/8.8.3) with ESMTP id BAA18803 for
 <cocoon-dev@xml.apache.org>; Wed, 20 Sep 2000 01:01:20 +0200
Message-ID: <39C7F0BC.B060350B@apache.org>
Date: Wed, 20 Sep 2000 01:03:24 +0200
From: Stefano Mazzocchi <stefano@apache.org>
Organization: Apache Software Foundation
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en,it
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [C2] Merging pipelines into a new pipeline
References: <E13bNC3-000La2-0A@finch-post-10.mail.demon.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

Stuart Roebuck wrote:
> 
> Can anyone point me in the right direction with this little problem.  I
> suspect there is an elegant solution in Cocoon 2, but I haven't found it in
> my trawling of the documentation and draft sitemap documents.
> 
> I basically want to merge the output (serialized) of two or more pipelines
> as the input (generator) of another.
> 
> Currently I do it by creating a dummy.xml file as the generator for a
> pipeline containing an XSLT translator which has code of the form:
> 
> <xsl:template match="dummy">
>     <new-group>
>         <xsl:apply-templates
> select="document('http://localhost:8080/context/pipe1.xml')/group/*" />
>         <xsl:apply-templates
> select="document('http://localhost:8080/context/pipe2.xml')/group/*" />
>     </new-group>
> </xsl:template>
> 
> This works, but it's not exactly elegant / scaleable / etc.
> 
> If I could do something like:
> 
>    <xsl:apply-templates select="document('cocoon://pipe1.xml')/group/*" />
>    <xsl:apply-templates select="document('cocoon://pipe2.xml')/group/*" />

Hmmmm, just stroke me, what about simply

  <xsl:apply-templates select="document('pipe1.xml')/group/*" />

then 

  <xsl:apply-templates select="document('file:///pipe1.xml')/group/*" />

if you wanted a file on the file system?

That way we don't have to extend URL and makes perfect sense to consider
the cocoon pipeline the current context.

What do you think?

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------
 Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------