Return-Path: 
 <cocoon-dev-return-29117-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 18272 invoked by uid 500); 4 Jul 2002 15:50:31 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 18261 invoked from network); 4 Jul 2002 15:50:31 -0000
Message-ID: <3D22BB9F.2BA79B9C@apache.org>
Date: Wed, 03 Jul 2002 10:53:51 +0200
From: Stefano Mazzocchi <stefano@apache.org>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [RT] reconsidering pipeline semantics
References: <3D21A28D.213AC669@apache.org> <3D22173D.4060208@yahoo.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

"J.Pietschmann" wrote:
> 
> Stefano Mazzocchi wrote:
> >  - deprecate 'internal-only' attribute of 'map:pipeline'
> >    [because named pipelines become implicitly internal-only]
> 
> I use something like the following:
> 
>    <div class="newsbox">
>      <xsl:for-each select=
>        "document(concat('cocoon://int/news/',$pubdir))/files/file">
>        <xsl:sort select="@last-modified"/>
>        <p class="newsheadline">
>          <xsl:value-of select="document(@name)/document/header/title">
>        </p>
>        <p class="newsabstract">
>          <xsl:value-of select="substring(
>          document(@name)/document/header/abstract,1,42)">
>        </p>
>      </xsl:for-each>
>    ...

I personally don't like the document() function of XSLT. I normally
suggest to use an xinclude stage to perform aggregation when the
structure of the aggregation is not fixed, but that's really up to you.

> and in the sitemap
>    <map:pipeline internal-only="yes">
>       <map:match pattern="int/news/*">
>         <map:generate type="directory" src="/my/news/{1}"/>
>         <map:transform src="xslt/newsfilter.xsl"/>
>         <map:serialize type="xml"/>
>       </map:match>
>    </map:pipeline>
> 
> Is there a better way to solve this kind of problem?
> (I worked around the caching issue).

if you use named pipelines you could do

    <map:pipeline name="news">
       <map:match pattern="*">
         <map:generate type="directory" src="/my/news/{1}"/>
         <map:transform src="xslt/newsfilter.xsl"/>
         <map:serialize type="xml"/>
       </map:match>
    </map:pipeline>

and then call it with

 pipeline://news/*

> How will this be solved without internal-only pipelines?
> The $pubdir is curently a parameter but there are reasons
> to have it been taken from input XML in some cases. In
> any case, aggregation seems not to be quite right.

Why? what's the problem you are experiencing?

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------



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