cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Agler" <ryanag...@hotmail.com>
Subject handle-errors skipped after first transformation
Date Thu, 12 Sep 2002 06:37:07 GMT
Hello,
Just wondering if this is a bug or I'm just missing something obvious:  

I have several places in my sitemap where there are multiple
transformations taking place
(generate-->transform-->transform-->serialize), and have experienced
random map:handle-errors behavior when exceptions would occur during the
transformation process.

I decided to do an experiment by modifying startElement in the
LogTransformer to throw a SAXException after it was called a few times,
and here is what I found:

If a SAXException occurs in a transformer that is located DIRECTLY AFTER
the generator
(generate-->transformThatThrowsException-->transform-->serialize),
map:handle-errors works properly.  However, if an exception occurs in a
transformer that comes AFTER THE FIRST transformer in the sitemap
(generate-->transform-->transformThatThrowsException-->serialize),
map:handle-errors doesn't seem to be getting called at all:  only a
blank html page gets returned to the client, even if I specify
map:handle-errors to serialize the error as xml.  This would also
explain why map:handle-errors works properly for all of the
single-transformation parts of my sitemap.

I am using the interpreted sitemap with Cocoon 2.1-dev.

Any thoughts?




---------------------------------------------------------------------
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:     <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>


Mime
View raw message