If you override the ExceptionReport page, that that's it; your apps' ExceptionReport overrrides the core library's ExceptionReport.
You should look into overriding the RequestExceptionHandler service; its job is to decide how to report an uncaught exception. You could add a product vs. development mode switch here to decide whether to use a page from your application to report the exception, or the default ExceptionReporter page. On Thu, Apr 10, 2008 at 6:14 AM, Peter Stavrinides <[EMAIL PROTECTED]> wrote: > Hi all > > I have implemented an exception page, not unlike: > http://wiki.apache.org/tapestry/Tapestry5ExceptionPage , but I haven't found > a way to revert to Tapestry's default exception page. It seems to be > overridden no matter what I try... does anyone know how can I switch this > on and off? > > Thanks > Peter > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
