Details
-
Type:
New Feature
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.9
-
Fix Version/s: 1.9.1
-
Component/s: Web - Tapestry
-
Labels:None
Description
If you are using Tapestry 4, you can change your hivemodule.xml as follows:
<contribution configuration-id="tapestry.InfrastructureOverrides">
<property name="exceptionPageName" value="ApplicationUnavailable"/>
</contribution>
Forgot to add that you'd also need to have a property or method named
"exception" in your custom exception page.
The property type is Throwable, which will be called by the Tapestry default
ExceptionPresenter.
You can see an example of this from the Vlib example in Tapestry 4.
Done, but commented-out in WEB-INF/hivemodule.xml. With this in place, the error messages from Tapestry are tough to figure out.
<!-- Uncomment before going to production as it displays nicer error messages to users -->
<!--<contribution configuration-id="tapestry.InfrastructureOverrides">
<property name="exceptionPageName" value="error"/>
</contribution>-->