Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.1.0
-
Component/s: None
-
Labels:None
Description
We should provide an exception page:
<contribution configuration-id="tapestry.Infrastructure"> <property name="exceptionPageName" value="ExceptionPage"/> </contribution>
Instead of the above, trails-core now contributes ExceptionPresenter that handles all TrailsRuntimeExceptions. It's not perfect now you cannot contribute you own implementation. A better way would have been ExceptionPresenter pipeline, but it would have required Hivemind 1.1.2. Read more about it in the comments in trails-core. The Trails ExceptionPresenter renders a DefaultException page, or if entity type is provided and a correspoding page is available, a <Type>Exception page.
You can still override the default Tapestry error page using the above syntax - which should make sense in a production environment