camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r833404 - in /websites/production/camel/content: cache/main.pageCache error-handling-in-camel.html
Date Sun, 30 Sep 2012 08:17:34 GMT
Author: buildbot
Date: Sun Sep 30 08:17:34 2012
New Revision: 833404

Production update by buildbot for camel


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

Modified: websites/production/camel/content/error-handling-in-camel.html
--- websites/production/camel/content/error-handling-in-camel.html (original)
+++ websites/production/camel/content/error-handling-in-camel.html Sun Sep 30 08:17:34 2012
@@ -114,13 +114,17 @@ This works great in the <a shape="rect" 
 <h3><a shape="rect" name="ErrorhandlinginCamel-Scopes"></a>Scopes</h3>
-<p>Camel supports 2 scopes for the non transactional type:</p>
-<ul class="alternate" type="square"><li>global</li><li>per route</li></ul>
+<p>Camel supports 2 scopes that is determined by the DSL in use:</p>
+<div class="table-wrap">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> DSL </th><th colspan="1" rowspan="1" class="confluenceTh">
Scope 1 </th><th colspan="1" rowspan="1" class="confluenceTh"> Scope 2 </th><th
colspan="1" rowspan="1" class="confluenceTh"> Note </th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> XML DSL </td><td colspan="1" rowspan="1"
class="confluenceTd"> CamelContext </td><td colspan="1" rowspan="1" class="confluenceTd">
route </td><td colspan="1" rowspan="1" class="confluenceTd"> Scope 2 takes precedence
over scope 1 </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
Java/Scala DSL </td><td colspan="1" rowspan="1" class="confluenceTd"> RouteBuilder
</td><td colspan="1" rowspan="1" class="confluenceTd"> route </td><td
colspan="1" rowspan="1" class="confluenceTd"> Scope 2 takes precedence over scope 1 </td></tr></tbody></table>
+<p>When using XML DSL then scope 1 applies for all routes. Where as when using Java
DSL then route 1 only applies for the given RouteBuilder instance. So if you have multiple
RouteBuilder's then each route builder has its own scope 1. </p>
-<p>And the same 2 scopes for transactional type:</p>
-<ul class="alternate" type="square"><li>global</li><li>per route
(using spring transaction policy)</li></ul>
+<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src=""
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">If
you want to share scope among RouteBuilder's you can use class inheritance and create a base
class, and then extend this class for your RouteBuilder's and invoke the super.configure()
+<p>Mind that there was a bug in Camel that affected the scopes when using multiple
RouteBuilder classes. See more details at <a shape="rect" class="external-link" href="">CAMEL-5456</a>.</p>
 <h3><a shape="rect" name="ErrorhandlinginCamel-HowdoestheDeadLetterChannelerrorhandlerwork"></a>How
does the <a shape="rect" href="dead-letter-channel.html" title="Dead Letter Channel">Dead
Letter Channel</a> error handler work</h3>
 <p>When Camel is started it will inspect the routes and weave in the error handling
into the routing. With up to 3 supported scopes, the error handling can be quite complex.
And on top of that you have inherited error handling and you can even configure <a shape="rect"
href="exception-clause.html" title="Exception Clause">Exception Clause</a>s to handle
specific exception types differently. So yes it's advanced but very powerful when you get
the grip of it.</p>

View raw message