DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12562>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12562 handle-errors skipped after first transformation Summary: handle-errors skipped after first transformation Product: Cocoon 2 Version: Current CVS Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: sitemap components AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
