>From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]]
<skip/>
>A pipeline may contain *all* components at the first level.
>
><note who="sm">having 'mount' and 'redirect-to' as first level
>components doesn't make really sense, but it doesn't hurt either so why
>should we limit it?</note>
>
>The order of the components defines their processing precedence.
>
>Pipeline processing is started from the top-most component and stopped
>when one of the 'ending' components are found:
>
> - serializer, reader
>
>If an error is triggered during pipeline processing, the output is
>detached from the pipeline and attached to the error-handling
>subpipeline.
>
><question who="SM">what happens when the client has already received
>part of the request (say during aggregation?)</question>
>
<shy:comment>
Hmmm for i.e. in a FOP serialization pipeline:
I think you have to send a new Request. Maybe a simple HTTP request with
the error message or something depending on the serializer.
Carsten proposed month ago something like an error generator.
</shy:comment>
<skip/>
Gerhard
-----------------------------------------------
Consciousness: that annoying time between naps.
-----------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
