Another month, another release. This time we bring you a Tapestry-style replacement for this standard web.xml configuration:
Tapestry conveniently wraps up any uncaught exception inside ComponentEventException and displays a very nice exception page at development time, but unfortunately that makes it impossible to use the standard error-page configuration in your web.xml. Not that configuring all that in verbose xml is that great anyway but it had its uses. tapestry-exceptionpage allows you to simply contribute the exception type/error page mappings in plain Java and allows specifing context for the error pages to make it quite a bit more flexible than the standard configuration. Check out the tapestry-exceptionpage guide for more info!