Vadim Gritsenko wrote:
Ralph Goers wrote:
Does this fix mean that handle-errors now works on internal pipelines as well?
No, not yet, I need couple of more days. But it means that:
<map:pipelines> <map:pipeline> ... <map:handle-errors/> (1) </map:pipeline> <map:handle-errors/> (2) </map:pipelines>
(2) is now behaving more like (1). Before, I noticed it did not log an error into handled-error log, did not handle ConnectionResetException, etc.
Sorry, I may have missed something as I never heard of (2). When is it triggered?
Also, when no match is found, the <handle-errors> of the last <map:pipeline> was used to handle the ResourceNotFound. Is this still the case?
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
