On 20.Aug.2002 -- 04:11 PM, Barbara Post wrote:
Barbara,
in short: you cannot. If you had a redirect after the response is
already produced, it would be ignored. In addition, you may not have a
pipeline with a generator but without a serializer (correction:
call-ressource may be the last, but eventually, there needs to be a
serializer).
> I have a series of transformers (last one inserts in a database) then want
I would consider it bad design to modify data in a transformer if the
result depends on the outcome.
> to go to another pipeline (anyway I have to do a generation from new xml,
> not the DB successful insertion message) without having interaction with the
> user, how can I do that ?
Apart from needing a serializer for this particular pipeline anyways,
you might get away using aggregation.
<map:aggregate>
<map:part src="pipeline-that-does-db-transform"/>
<map:part src="pipeline-that-does-real-work"/>
<map:aggregate>
Difficult to pass a parameter from part one to part two,
though. Request or session attributes would do.
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
