Hi Paul,

a normal error-handling could look like the following (taken from samples sitemap):

<map:handle-errors>
<map:transform src="context://samples/stylesheets/system/error2html.xsl"/>
<map:serialize status-code="500"/>
</map:handle-errors>

If you use another XSL for it, you can at least change the layout or style of the error message. Or do you need more?

Regards,

Joerg

Reeves, Paul wrote:
Is there a way to catch the internal cocoon errors e.g. Resource not found
and handle them ??

I would like to produce a more elegant method of reporting back to the user
by being able to customise the xsl to provide a more project specfic report and user friendly
page.
I searched around the 'documentation' and Wiki etc and can handle other
pipeline errors with the map:handle-errors directive but this does not appear to work for internal
cocoon errors such as that
mentioned above.

Thanks in advance,
Paul

---------------------------------------------------------------------
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:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Reply via email to