At 11:08 am +0100 19/3/02, Nicola Ken Barozzi wrote:
>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.
>>
>> When ever a component in my app throws an exception, I get my (partial)
>> processed XML (as expected) but it is followed by the error definition.
>>
>> That is, I get _two_document_roots_ !!!!
>>
>> How are we supposed to do anything with this? ;)
>>
>
>Dear Jeremy,
> this is a known issue, and basically a worksforme.
>
>Since we use SAX, and the processing is incremental, to augment the users
>percieved performance and decrease memory usage we send the results as soon
>as they are ready.
>
>This means that the error happens when partial results are already
>committed, and error info can only follow already committed output.
>
>If you want you can change the error stylesheet to have inside a javascript
>that redirects the user to a clean error page, or simply output a <p> tag
>that says that an error occurred.
Ah, can I redirect on error internally and still have the original Request
available?
Basically I am trying to send sensible response when StreamGenerator throws
exceptions on mal-formed XML.
>If you have a better solution, please commit it, we are all waiting.
Yea, sorry if I was rude !
I accept what you say ..... I think that the current error-handling is ok
for publishing, but not good enough for webapps ......
Has anyone got examples they can send me of how they have implemented
error-handling in the sitemap, the samples are not very revealing .....
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]
