Custom Exception Page
When Tapestry detects an uncaught exception, it displays an "exception" page.
To see the current "exception" page, click here:
Throw an Exception!
Tapestry's default exception page, called Exception, is excellent during development because it contains a
wealth of technical information. However, it's not usually suitable for a production environment, where what's usually
needed is a simple message and absolutely no data about the internals of the application and server.
JumpStart includes an example of a custom exception page, called UserFriendlySystemExceptionPage. To enable
it, you just copy a hivemodule.xml file to the environment, as explained in web/src/main/examples/conf/README.txt.
Once it is enabled, you can click on the link above to test it.
An exception handling strategy
If you're unsure which exceptions should be handled on your current page and which ones should result in the exception page,
then try splitting them according to these 2 categories:
- Application exceptions, such as validation errors. These can be displayed on the page that detects them.
- System exceptions, such as system availability problems (eg. cannot connect to
database) and irrecoverable errors (eg. OutOfBoundsException, IllegalStateException). These can be handled by rethrowing or not catching at all,
causing the exception page to be shown.
To Login