tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r976116 - in /websites/production/tapestry/content: cache/main.pageCache overriding-exception-reporting.html
Date Tue, 22 Dec 2015 04:20:01 GMT
Author: buildbot
Date: Tue Dec 22 04:20:01 2015
New Revision: 976116

Log:
Production update by buildbot for tapestry

Modified:
    websites/production/tapestry/content/cache/main.pageCache
    websites/production/tapestry/content/overriding-exception-reporting.html

Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/tapestry/content/overriding-exception-reporting.html
==============================================================================
--- websites/production/tapestry/content/overriding-exception-reporting.html (original)
+++ websites/production/tapestry/content/overriding-exception-reporting.html Tue Dec 22 04:20:01
2015
@@ -131,7 +131,7 @@
                         
                     </div>
     </li></ul>
-</div><p>Of course, one of the first questions anyone asks is "How do I turn
it off?" This exception reporting is very helpful for developers but its easy to see it as
terrifying for potential users. Not that you'd have have runtime exceptions in production,
of course, but even so ...</p><h2 id="OverridingExceptionReporting-Version1:ReplacingtheExceptionReportPage">Version
1: Replacing the Exception Report Page</h2><p>Let's start with a page that fires
an exception from an event handler method.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ActionFail.tml</b></div><div
class="codeContent panelContent pdl">
+</div><p>Of course, one of the first questions anyone asks is "How do I turn
it off?" This exception reporting is very helpful for developers but its easy to see it as
terrifying for potential users. Catching runtime exceptions can be a very useful way of handling
rarely occurring exceptions even in production, and there's no reason to throw away Tapestry's
default error reporting just to handle a few specific exceptions. From version 5.4 (for previous
versions, the functionality is available as an external, third-party module tapestry-exceptionpage),
you can contribute exception handles and/or exception pages for specific exception types.
Refer back to <a  href="runtime-exceptions.html">Runtime Exceptions</a> page for
more information. Read on if you want to completely replace Tapestry's default exception handling.</p><h2
id="OverridingExceptionReporting-Version1:ReplacingtheExceptionReportPage">Version 1: Replacing
the Exception Report Page</h2><p>Let's start with a page that fire
 s an exception from an event handler method.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ActionFail.tml</b></div><div
class="codeContent panelContent pdl">
 <pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;"> &lt;html
xmlns:t="http://tapestry.apache.org/schema/tapestry_5_4.xsd" t:type="layout" title="Action
Fail"&gt;
         &lt;p&gt;
             &lt;t:actionlink t:id="fail" class="btn btn-large btn-warning"&gt;Click
for Exception&lt;/t:actionlink&gt;



Mime
View raw message