|Tapestry-exceptionpage has graduated! As part of https://issues.apache.org/jira/browse/TAP5-1833, a version of tapestry-exceptionpage has been merged into Tapestry 5.4 core. Use the external dependency only for Tapestry versions before 5.4.|
In your Tapestry 5 applications, are you missing the standard error-page/exception-type configuration option specified by the servlet spec? For some rarely occurring exceptions, it's simpler to just catch them at the outermost layer of your application rather than carry a typed exception through multiple layers of abstractions just so you could show a sensible error message to the user, especially if you can't do anything more clever about it anyway. Unfortunately Tapestry wraps up all of your exceptions inside a ComponentEventException making the error-page/exception-type configuration in your web.xml useless. The default Tapestry 5 exception page is great for development but typically, you don't want to show that in production.