Our custom Engine class overrode activateExceptionPage(). It checked a configuration property (read from a properties file on startup) to tell whether it was running on a production server. If so, it presented a user-friendly error page and emailed the exception to us. If not, it logged the exception and called super.activateExceptionPage() to present Tapestry's detailed exception page.
Dan Adams wrote: >I found lots of great info on how to create a custom exception page, but >I'm wondering if anyone has a good way to make the custom error page >only appear in a production deploy and not in a testing deploy. > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
