cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Park, Paul" <>
Subject RE: [RT] reconsidering pipeline semantics
Date Tue, 02 Jul 2002 16:30:14 GMT
Will the pipelines support parameters?

Since, its begining to look like named xslt templates, what about something

   <pipeline name="blah">
      <param name="foo"/>
      <generate ../>
      <transform ../>
      <serialize ../>

   <call pipeline="blah">
      <with-param name="foo" value="bar"/>

-----Original Message-----
From: Stefano Mazzocchi []
Sent: Tuesday, July 02, 2002 5:55 AM
To: Apache Cocoon
Subject: [RT] reconsidering pipeline semantics


[using a pipeline as a pipeline] (as today)

    <match pattern="*">
     <call pipeline="blah"/>


So, here is what I propose:

 - add the 'pipeline' attribute to 'map:call'
 - add the 'name' attribute to 'map:pipeline'
 - deprecate the 'map:resources' element
 - deprecate 'internal-only' attribute of 'map:pipeline' 
   [because named pipelines become implicitly internal-only]
 - allow 'map:call' to be executed in any place, performing the pipeline
overloading behavior I explained above.

What do you think?  

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

To unsubscribe, e-mail:
For additional commands, email:

To unsubscribe, e-mail:
For additional commands, email:

View raw message