2009/4/8 Dr. Bhatia Praveen <[email protected]>: > Thanks. It does work. > For others, like me :) , here is simple example that I could make work:
You are welcome - thanks for following up - very handy for others. Ross > > <map:match pattern="**P1.xml"> > <map:generate src="cocoon:/P.xml"/> > <map:serialize type="xml"/> > </map:match> > > This example would call the P pipeline from P1 pipeline. > > thanks > Praveen > > ----- Original Message ----- From: "Ross Gardler" <[email protected]> > To: <[email protected]>; "Dr. Bhatia Praveen" > <[email protected]> > Sent: Tuesday, April 07, 2009 8:00 PM > Subject: Re: How to do common pipelines? > > > 2009/4/7 Dr. Bhatia Praveen <[email protected]>: >> >> Hello, >> Would like to use a pipeline, p, which is commonly used by other >> pipelines, p1, p2, p3. >> >> How could one achieve in p1, a call to common pipeline p, and then >> continue >> the processing into pipeline. >> (It sounds more like a functional call. In function parlance, it is >> equivalent to a function calling another function within itself and >> continuing forward after the function returns). > > Use the "cocoon:" protocol. See the forrest sitemaps for loads of > exampls, e.g. > http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/forrest.xmap > > Ross > > > > -- > Ross Gardler > > OSS Watch - supporting open source in education and research > http://www.oss-watch.ac.uk > > > > -------------------------------------------------------------------------------- > > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.238 / Virus Database: 270.11.42/2042 - Release Date: 04/05/09 > 10:54:00 > > -- Ross Gardler OSS Watch - supporting open source in education and research http://www.oss-watch.ac.uk
