cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Horst Rutter" <>
Subject Re: processing serializer output on server
Date Sun, 05 May 2002 06:31:08 GMT
What do you mean by "the Generator of the second calls the output of the first one"?
Are you refering to a map:call or a "cocoon:/smth" parameter? 
Could you please give a short example?

Here is what I have right now:
Also to correct myself I am dealing with one pipeline containing two <map:match> fragments
rather than 2 pipelines.

  <map:match pattern="generatepdf">
    <map:generate src=""/>
    <map:serialize type="fo2pdf"/>
  <map:match pattern="sendpdf">
    <map:generate type="serverpages" src="sendmail.xsp">
      <map:parameter name="email-attachment" value:"cocoon:/generatepdf"/>

I could also use an action (SendmailAction) instead of the xsp but that does not ease the
I'd still have to pass on or call in to generatepdf and put that into a parameter for the

BTW I believe a construct similar to action-set could help in a situation like this where

    <map:pipeline id="first" ... </map:pipeline>
    <map:pipeline id="second" ... </map:pipeline>
always ensures the contained pipelines get executed in the order defined and always pass
on the output of the previous one as the input for the next in sequence.
Further elaborating we could also have something similar for ensuring *all* matching <map:match>
fragments in
a pipeline get processed sequentially for instance by having a parameter on <map:pipeline>


----- Original Message ----- 
From: "Nicola Ken Barozzi" <>
To: <>
Sent: Saturday, May 04, 2002 1:35 AM
Subject: Re: processing serializer output on server

> From: "Horst Rutter" <>
> > Hi all,
> > Is it possible to do some postprocessing using the output of a serializer
> > before the pipeline is finished for consumation by the client?
> >
> > I have looked around but did not find any proper sitemap construct.
> > I also did not find anything allowing what I would call "pipeline
> chaining".
> >
> > For example:
> > I would like to send off an email from the server containing a pdf file
> produced by the FOPserializer.
> > I have a pipeline that generates the pdf.
> > I also have another pipeline that is capable of sending an email.
> > What's the missing link here?
> You can use the output of a pipeline as the input to another pipeline.
> Simple call the last one and have the Generator of that one call the output
> of the first one.
> You can tag the first one as internal to make it unusable from the outside.
> Now that I think of it, hey, we can make a ZipperReader that sends the
> content zipped :-D
> --
> Nicola Ken Barozzi         
>             - verba volant, scripta manent -
>    (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

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

View raw message