cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Quinn <je...@media.demon.co.uk>
Subject error handling !*#%!
Date Tue, 19 Mar 2002 09:38:56 GMT
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? ;)

I thought I should be able to insert multiple <map:handle-error/> in
individual pipelines to catch that particular problem, this does not appear
to work.

What I hope to be able to do is this:

I have pipelines that assemble via aggregation, from other internal pipelines.
If one of those internal pipelines has an error, I get the error XML rather
than the content it would have produced ...... this way I can at least
respond to the error ......

Is this possible?


thanks for any help

regards Jeremy

-- 
   ___________________________________________________________________

   Jeremy Quinn                                           Karma Divers
                                                       webSpace Design
                                            HyperMedia Research Centre

   <mailto:sharkbait@mac.com>     		 <http://www.media.demon.co.uk>
   <phone:+44.[0].20.7737.6831>             <pager:jermq@vizzavi.net>

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message