Will the pipelines support parameters?
Since, its begining to look like named xslt templates, what about something
like
<pipeline name="blah">
<param name="foo"/>
<generate ../>
<transform ../>
<serialize ../>
</pipeline>
<call pipeline="blah">
<with-param name="foo" value="bar"/>
</call>
-----Original Message-----
From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 5:55 AM
To: Apache Cocoon
Subject: [RT] reconsidering pipeline semantics
<snip/>
[using a pipeline as a pipeline] (as today)
<pipeline>
<match pattern="*">
<call pipeline="blah"/>
</match>
</pipeline>
<snip/>
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.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
