At 7:59 am -0500 19/3/02, Vadim Gritsenko wrote:
>> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
>>
>> From: "Jeremy Quinn" <[EMAIL PROTECTED]>
>>
>> > Dear All,
>> >
>> > I am totally mystified as to how you are supposed to handle errors
>in
>> > webapps built using Cocoon.
>> If you have a better solution, please commit it, we are all waiting.
>
>This reminds me of TODO item (in the todo.xml):
>----
> <action context="code">
> Check how to handle the mixing of output streams when an error inside
> a pipeline occurs. When the pipeline has something written to the
> output stream and then an error occurs the result is the first
>written
> part with the appended exception.
> One solution could be a configurable intermediate output stream.
> </action>
>----
>
>Jeremy, that's what you want, isn't it?
I am not sure ..... ;)
If an internal pipeline makes an error, and has it's own error-handler, I
would hope that error could be inline, not tacked on at the end of all
processing, though I am obviously not understanding what is going on well
enough right now.
regards Jeremy
--
___________________________________________________________________
Jeremy Quinn Karma Divers
webSpace Design
HyperMedia Research Centre
<mailto:[EMAIL PROTECTED]> <http://www.media.demon.co.uk>
<phone:+44.[0].20.7737.6831> <pager:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
