author | Michael Krelin <hacker@klever.net> | 2005-01-30 00:57:53 (UTC) |
---|---|---|
committer | Michael Krelin <hacker@klever.net> | 2005-01-30 00:57:53 (UTC) |
commit | 71f4cc84c3788c6904ede17cd626a9ca9c349e3b (patch) (side-by-side diff) | |
tree | cfe7736ae3416ad314b7451b756e587335c357c7 /htdocs/exceptions/runtime.chtml | |
parent | acd2a536dd6bb3ef9438482725f77ac9044ae79b (diff) | |
download | sitecing-71f4cc84c3788c6904ede17cd626a9ca9c349e3b.zip sitecing-71f4cc84c3788c6904ede17cd626a9ca9c349e3b.tar.gz sitecing-71f4cc84c3788c6904ede17cd626a9ca9c349e3b.tar.bz2 |
initial commit into repository
Diffstat (limited to 'htdocs/exceptions/runtime.chtml') (more/less context) (show whitespace changes)
-rw-r--r-- | htdocs/exceptions/runtime.chtml | 47 |
1 files changed, 47 insertions, 0 deletions
diff --git a/htdocs/exceptions/runtime.chtml b/htdocs/exceptions/runtime.chtml new file mode 100644 index 0000000..d0a8e14 --- a/dev/null +++ b/htdocs/exceptions/runtime.chtml @@ -0,0 +1,47 @@ +% html(); return; /* vim:set ft=sitecing: */ +%%derive layout = "/ancestry/layout.chtml"; +<%constructor> + b_strict = false; +</%constructor> +<%codemethod string title() %> + return "runtime exceptions handling"; +</%codemethod> +<%method void content() %> + <h1>site-C-ing runtime exception handling</h1> + <p> + The component may throw an exception while executing and the + <em>site-C-ing</em> will gladly pass it to the handler component which will + give the user appropriate output (unless it throws an exception itself, of + course). Here you will see an example output provided by the handler bundled + with the <em>site-C-ing</em>. + </p> + + <p> + Suppose you have <a href="/view/htdocs/exceptions/development/runtime.chtml" + target="insert" title="the link opens in the frame below">a component</a>, + which at some point throws an exception. Of course, <em>site-C-ing</em> will + catch the exception and pass it to <a + href="/view/htdocs/handlers/exception_dev" target="insert" title="the link + opens in the frame below">the handler</a>, specified in <a + href="/view/htdocs/exceptions/development/.scrc" target="insert" title="the + link opens in the frame below">the configuration file</a>, which will produce + some nice, human-readable <a href="/exceptions/development/runtime" + target="insert" title="the link opens in the frame below">output</a>. Well, + you may not wish to give out all this information in the production + environment, so you just put in your <a + href="/view/htdocs/exceptions/production/.scrc" target="insert" title="the + link opens in the frame below">configuration file</a> some <a + href="/view/htdocs/handlers/exception_prod" target="insert" title="the link + opens in the frame below">different handler</a>, which just gives user <a + href="/exceptions/production/runtime" target="insert" title="the link opens + in the frame below">a friendly yet lame excuse</a>. + </p> + + <div class="insert"> + <iframe id="insert" name="insert" src="about:blank" width="95%" height="300"> + <p>I wanted to put an <iframe> here, but your browser does not seem to + support it. That is okay, it still will open links somehow.</p> + </iframe> + </div> + +</%method> |