Donald Ball wrote:
> I'm interested in something along these lines as well. Currently, I wrap
> my library method calls with a big try/catch block and dump the stack
> trace to System.err. What I'd ideally like to be able to do is either
> display the error using the standard cocoon frontend, send a 500 error, or
> create an error XML node in the result document, configurable on a
> per-file or per-directory basis.
>
> - donald
Yeah, I'd like to be able to forward the request onto a error.xsp file or
something like that lets you generate a page using xsl templates depending
on the error.
MIke
|