cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Error handling with nested Velocity components
Date Mon, 15 Apr 2002 13:42:22 GMT

Does anyone know how to force a new page on the browser when dealing with
errors that come from a nested Velocity component?  I'm finding that with my
current pipeline:

     <map:transform type="xslt" src="error/tidyerror.htm"/>
     <map:serialize type="html" status-code="500"/>

causes the error to appear within the page, in the same way that the
Velocity component would have done. What I need is for the error page to be
a complete page, replacing any components that may already have been
displayed when processing that request.



Please check that your question has not already been answered in the
FAQ before posting. <>

To unsubscribe, e-mail: <>
For additional commands, e-mail: <>

View raw message