camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r867338 [2/4] - in /websites/production/camel/content: book-in-one-page.html book-pattern-appendix.html cache/main.pageCache camel-2120-release.html polling-consumer.html
Date Tue, 25 Jun 2013 07:18:29 GMT

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Tue Jun 25 07:18:29 2013
@@ -36,6 +36,18 @@
     <![endif]-->
 
 
+  <link href='http://camel.apache.org/styles/highlighter/styles/shCore.css' rel='stylesheet' type='text/css' />
+  <link href='http://camel.apache.org/styles/highlighter/styles/shThemeEclipse.css' rel='stylesheet' type='text/css' />
+  <script src='http://camel.apache.org/styles/highlighter/scripts/shCore.js' type='text/javascript'></script>
+  <script src='http://camel.apache.org/styles/highlighter/scripts/shBrushSql.js' type='text/javascript'></script>
+  <script src='http://camel.apache.org/styles/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
+  <script src='http://camel.apache.org/styles/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
+  <script src='http://camel.apache.org/styles/highlighter/scripts/shBrushPlain.js' type='text/javascript'></script>
+  
+  <script type="text/javascript">
+  SyntaxHighlighter.defaults['toolbar'] = false;
+  SyntaxHighlighter.all();
+  </script>
 
     <title>
     Apache Camel: Book In One Page
@@ -121,47 +133,70 @@ There's a great discussion about Camel a
 
 <p>We start with creating a <a shape="rect" href="camelcontext.html" title="CamelContext">CamelContext</a> - which is a container for <a shape="rect" href="components.html" title="Components">Components</a>, <a shape="rect" href="routes.html" title="Routes">Routes</a> etc:</p>
 
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>CamelContext context = new DefaultCamelContext();</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+CamelContext context = new DefaultCamelContext();
+]]></script>
+</div></div>
 
 <p>There is more than one way of adding a Component to the CamelContext. You can add components implicitly - when we set up the routing - as we do here for the <a shape="rect" href="file2.html" title="File2">FileComponent</a>:</p>
 
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>context.addRoutes(new RouteBuilder() {<br clear="none">
-    public void configure() </p>
-<div class="error"><span class="error">Unknown macro: {        from("test-jms}</span> </div>
-<p>});</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+context.addRoutes(new RouteBuilder() {
+    public void configure() {
+        from("test-jms:queue:test.queue").to("file://test");
+    }
+});
+]]></script>
+</div></div>
 
 
 <p>or explicitly - as we do here when we add the JMS Component:</p>
 
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>ConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://localhost?broker.persistent=false");<br clear="none">
-// Note we can explicit name the component<br clear="none">
-context.addComponent("test-jms", JmsComponent.jmsComponentAutoAcknowledge(connectionFactory));</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+ConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://localhost?broker.persistent=false");
+// Note we can explicit name the component
+context.addComponent("test-jms", JmsComponent.jmsComponentAutoAcknowledge(connectionFactory));
+]]></script>
+</div></div>
 
 <p>The above works with any JMS provider. If we know we are using <a shape="rect" href="activemq.html" title="ActiveMQ">ActiveMQ</a> we can use an even simpler form using the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.5.0/activemq-camel/apidocs/org/apache/activemq/camel/component/ActiveMQComponent.html#activeMQComponent%28java.lang.String%29"><tt>activeMQComponent()</tt> method</a> while specifying the <a shape="rect" class="external-link" href="http://activemq.apache.org/configuring-transports.html">brokerURL</a> used to connect to ActiveMQ </p>
 
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>camelContext.addComponent("activemq", activeMQComponent("vm://localhost?broker.persistent=false"));</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+camelContext.addComponent("activemq", activeMQComponent("vm://localhost?broker.persistent=false"));
+]]></script>
+</div></div>
 
 <p>In normal use, an external system would be firing messages or events directly into Camel through one if its <a shape="rect" href="components.html" title="Components">Components</a>  but we are going to use the <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/ProducerTemplate.html">ProducerTemplate</a> which is a really easy way for testing your configuration:</p>
 
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>ProducerTemplate template = context.createProducerTemplate();</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+ProducerTemplate template = context.createProducerTemplate();
+]]></script>
+</div></div>
 
 <p>Next you <b>must</b> start the camel context. If you are using <a shape="rect" href="spring.html" title="Spring">Spring</a> to configure the camel context this is automatically done for you; though if you are using a pure Java approach then you just need to call the start() method</p>
 
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>camelContext.start();</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+camelContext.start();
+]]></script>
+</div></div>
 
 <p>This will start all of the configured routing rules.</p>
 
 <p>So after starting the <a shape="rect" href="camelcontext.html" title="CamelContext">CamelContext</a>, we can fire some objects into camel:</p>
 
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>for (int i = 0; i &lt; 10; i++) {<br clear="none">
-    template.sendBody("test-jms:queue:test.queue", "Test Message: " + i);<br clear="none">
-}</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+for (int i = 0; i &lt; 10; i++) {
+    template.sendBody("test-jms:queue:test.queue", "Test Message: " + i);
+}
+]]></script>
+</div></div>
 
 
 <h2><a shape="rect" name="BookInOnePage-Whathappens%3F"></a>What happens?</h2>
@@ -188,53 +223,73 @@ context.addComponent("test-jms", JmsComp
 
 
 <p>This can be created in a route like this:</p>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>&lt;route&gt;<br clear="none">
-   &lt;from uri="jms:queue:order"/&gt;<br clear="none">
-   &lt;pipeline&gt;<br clear="none">
-      &lt;bean ref="validateOrder"/&gt;<br clear="none">
-      &lt;bean ref="registerOrder"/&gt;<br clear="none">
-      &lt;bean ref="sendConfirmEmail"/&gt;<br clear="none">
-   &lt;/pipeline&gt;<br clear="none">
-&lt;/route&gt;</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
+&lt;route&gt;
+   &lt;from uri="jms:queue:order"/&gt;
+   &lt;pipeline&gt;
+      &lt;bean ref="validateOrder"/&gt;
+      &lt;bean ref="registerOrder"/&gt;
+      &lt;bean ref="sendConfirmEmail"/&gt;
+   &lt;/pipeline&gt;
+&lt;/route&gt;
+]]></script>
+</div></div>
 
 <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="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Pipeline is default</b><br clear="none">In the route above we specify <tt>pipeline</tt> but it can be omitted as its default, so you can write the route as:
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>&lt;route&gt;<br clear="none">
-   &lt;from uri="jms:queue:order"/&gt;<br clear="none">
-   &lt;bean ref="validateOrder"/&gt;<br clear="none">
-   &lt;bean ref="registerOrder"/&gt;<br clear="none">
-   &lt;bean ref="sendConfirmEmail"/&gt;<br clear="none">
-&lt;/route&gt;</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
+&lt;route&gt;
+   &lt;from uri="jms:queue:order"/&gt;
+   &lt;bean ref="validateOrder"/&gt;
+   &lt;bean ref="registerOrder"/&gt;
+   &lt;bean ref="sendConfirmEmail"/&gt;
+&lt;/route&gt;
+]]></script>
+</div></div>
 <p>This is commonly used not to state the pipeline. </p>
 
 <p>An example where the pipeline needs to be used, is when using a multicast and "one" of the endpoints to send to (as a logical group) is a pipeline of other endpoints. For example.</p>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>&lt;route&gt;<br clear="none">
-   &lt;from uri="jms:queue:order"/&gt;<br clear="none">
-   &lt;multicast&gt;<br clear="none">
-     &lt;to uri="log:org.company.log.Category"/&gt;<br clear="none">
-     &lt;pipeline&gt;<br clear="none">
-       &lt;bean ref="validateOrder"/&gt;<br clear="none">
-       &lt;bean ref="registerOrder"/&gt;<br clear="none">
-       &lt;bean ref="sendConfirmEmail"/&gt;<br clear="none">
-     &lt;/pipeline&gt;<br clear="none">
-   &lt;/multicast&gt;<br clear="none">
-&lt;/route&gt;</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
+&lt;route&gt;
+   &lt;from uri="jms:queue:order"/&gt;
+   &lt;multicast&gt;
+     &lt;to uri="log:org.company.log.Category"/&gt;
+     &lt;pipeline&gt;
+       &lt;bean ref="validateOrder"/&gt;
+       &lt;bean ref="registerOrder"/&gt;
+       &lt;bean ref="sendConfirmEmail"/&gt;
+     &lt;/pipeline&gt;
+   &lt;/multicast&gt;
+&lt;/route&gt;
+]]></script>
+</div></div>
 
 <p>The above sends the order (from <tt>jms:queue:order</tt>) to two locations at the same time, our log component, and to the "pipeline" of beans which goes one to the other. If you consider the opposite, sans the <tt>&lt;pipeline&gt;</tt></p>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>&lt;route&gt;<br clear="none">
-   &lt;from uri="jms:queue:order"/&gt;<br clear="none">
-   &lt;multicast&gt;<br clear="none">
-     &lt;to uri="log:org.company.log.Category"/&gt;<br clear="none">
-     &lt;bean ref="validateOrder"/&gt;<br clear="none">
-     &lt;bean ref="registerOrder"/&gt;<br clear="none">
-     &lt;bean ref="sendConfirmEmail"/&gt;<br clear="none">
-   &lt;/multicast&gt;<br clear="none">
-&lt;/route&gt;</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
+&lt;route&gt;
+   &lt;from uri="jms:queue:order"/&gt;
+   &lt;multicast&gt;
+     &lt;to uri="log:org.company.log.Category"/&gt;
+     &lt;bean ref="validateOrder"/&gt;
+     &lt;bean ref="registerOrder"/&gt;
+     &lt;bean ref="sendConfirmEmail"/&gt;
+   &lt;/multicast&gt;
+&lt;/route&gt;
+]]></script>
+</div></div>
 
 <p>you would see that multicast would not "flow" the message from one bean to the next, but rather send the order to all 4 endpoints (1x log, 3x bean) in parallel, which is not (for this example) what we want. We need the message to flow to the validateOrder, then to the registerOrder, then the sendConfirmEmail so adding the pipeline, provides this facility.</p></td></tr></table></div>
 
 <p>Where as the <tt>bean ref</tt> is a reference for a spring bean id, so we define our beans using regular Spring XML as:</p>
 
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>   &lt;bean id="validateOrder" class="com.mycompany.MyOrderValidator"/&gt;</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
+   &lt;bean id="validateOrder" class="com.mycompany.MyOrderValidator"/&gt;
+]]></script>
+</div></div>
 
 <p>Our validator bean is a plain POJO that has no dependencies to Camel what so ever. So you can implement this POJO as you like. Camel uses rather intelligent <a shape="rect" href="bean-binding.html" title="Bean Binding">Bean Binding</a> to invoke your POJO with the payload of the received message. In this example we will <b>not</b> dig into this how this happens. You should return to this topic later when you got some hands on experience with Camel how it can easily bind routing using your existing POJO beans.</p>
 
@@ -246,12 +301,16 @@ context.addComponent("test-jms", JmsComp
 <h3><a shape="rect" name="BookInOnePage-UsingCamelComponents"></a>Using Camel Components</h3>
 <p>In the route lets imagine that the registration of the order has to be done by sending data to a TCP socket that could be a big mainframe. As Camel has many <a shape="rect" href="components.html" title="Components">Components</a> we will use the camel-mina component that supports <a shape="rect" href="mina.html" title="MINA">TCP</a> connectivity. So we change the route to:</p>
 
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>&lt;route&gt;<br clear="none">
-   &lt;from uri="jms:queue:order"/&gt;<br clear="none">
-   &lt;bean ref="validateOrder"/&gt;<br clear="none">
-   &lt;to uri="mina:tcp://mainframeip:4444?textline=true"/&gt;<br clear="none">
-   &lt;bean ref="sendConfirmEmail"/&gt;<br clear="none">
-&lt;/route&gt;</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
+&lt;route&gt;
+   &lt;from uri="jms:queue:order"/&gt;
+   &lt;bean ref="validateOrder"/&gt;
+   &lt;to uri="mina:tcp://mainframeip:4444?textline=true"/&gt;
+   &lt;bean ref="sendConfirmEmail"/&gt;
+&lt;/route&gt;
+]]></script>
+</div></div>
 
 <p>What we now have in the route is a <tt>to</tt> type that can be used as a direct replacement for the bean type. The steps is now:<br clear="none">
 1. payload from the <a shape="rect" href="jms.html" title="JMS">JMS</a> is sent as input to the validateOrder bean<br clear="none">
@@ -259,12 +318,16 @@ context.addComponent("test-jms", JmsComp
 3. the output from mainframe is sent back as input to the sendConfirmEmai bean</p>
 
 <p>What to notice here is that the <tt>to</tt> is not the end of the route (the world <img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/wink.gif" height="20" width="20" alt="" border="0">) in this example it's used in the middle of the <a shape="rect" href="pipes-and-filters.html" title="Pipes and Filters">Pipes and Filters</a>. In fact we can change the <tt>bean</tt> types to <tt>to</tt> as well:</p>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>&lt;route&gt;<br clear="none">
-   &lt;from uri="jms:queue:order"/&gt;<br clear="none">
-   &lt;to uri="bean:validateOrder"/&gt;<br clear="none">
-   &lt;to uri="mina:tcp://mainframeip:4444?textline=true"/&gt;<br clear="none">
-   &lt;to uri="bean:sendConfirmEmail"/&gt;<br clear="none">
-&lt;/route&gt;</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
+&lt;route&gt;
+   &lt;from uri="jms:queue:order"/&gt;
+   &lt;to uri="bean:validateOrder"/&gt;
+   &lt;to uri="mina:tcp://mainframeip:4444?textline=true"/&gt;
+   &lt;to uri="bean:sendConfirmEmail"/&gt;
+&lt;/route&gt;
+]]></script>
+</div></div>
 
 <p>As the <tt>to</tt> is a generic type we must state in the uri scheme which component it is. So we must write <b>bean:</b> for the <a shape="rect" href="bean.html" title="Bean">Bean</a> component that we are using.</p>
 
@@ -292,8 +355,11 @@ One of the most famous patterns books is
 <h3><a shape="rect" name="BookInOnePage-Ausefultipfornavigatingtheonlinedocumentation"></a>A useful tip for navigating the online documentation</h3>
 <p>The breadcrumbs at the top of the online Camel documentation can help you navigate between parent and child subsections.  <br clear="none">
 For example, If you are on the "Languages" documentation page then the left-hand side of the reddish bar contains the following links.</p>
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>Apache Camel &gt; Documentation &gt; Architecture &gt; Languages</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+Apache Camel &gt; Documentation &gt; Architecture &gt; Languages
+]]></script>
+</div></div>
 <p>As you might expect, clicking on "Apache Camel" takes you back to the home page of the Apache Camel project, and clicking on "Documentation" takes you to the main documentation page. You can interpret the "Architecture" and "Languages" buttons as indicating you are in the "Languages" section of the "Architecture" chapter. Adding browser bookmarks to pages that you frequently reference can also save time.  </p>
 
 <p><a shape="rect" name="BookInOnePage-onlinejavadocdocs"></a></p>
@@ -342,29 +408,44 @@ To date, URNs are not (yet) as popular a
 <h3><a shape="rect" name="BookInOnePage-Components"></a>Components</h3>
 <p><em>Component</em> is confusing terminology; <em>EndpointFactory</em> would have been more appropriate because a <tt>Component</tt> is a factory for creating <tt>Endpoint</tt> instances. For example, if a Camel-based application uses several JMS queues then the application will create one instance of the <tt>JmsComponent</tt> class (which implements the <tt>Component</tt> interface), and then the application invokes the <tt>createEndpoint()</tt> operation on this <tt>JmsComponent</tt> object several times. Each invocation of <tt>JmsComponent.createEndpoint()</tt> creates an instance of the <tt>JmsEndpoint</tt> class (which implements the <tt>Endpoint</tt> interface). Actually, application-level code does not invoke <tt>Component.createEndpoint()</tt> directly. Instead, application-level code normally invokes <tt>CamelContext.getEndpoint()</tt>; internally, the <tt>CamelContext</tt> object finds the desired <tt>Component</tt> object (as I will discuss shortly) and then inv
 okes <tt>createEndpoint()</tt> on it.<br clear="none">
 Consider the following code.</p>
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>myCamelContext.getEndpoint("pop3://john.smith@mailserv.example.com?password=myPassword");</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+myCamelContext.getEndpoint("pop3://john.smith@mailserv.example.com?password=myPassword");
+]]></script>
+</div></div>
 <p>The parameter to <tt>getEndpoint()</tt> is a URI. The URI <em>prefix</em> (that is, the part before ":") specifies the name of a component. Internally, the <tt>CamelContext</tt> object maintains a mapping from names of components to <tt>Component</tt> objects. For the URI given in the above example, the <tt>CamelContext</tt> object would probably map the <tt>pop3</tt> prefix to an instance of the <tt>MailComponent</tt> class. Then the <tt>CamelContext</tt> object invokes <tt>createEndpoint("pop3://john.smith@mailserv.example.com?password=myPassword")</tt> on that <tt>MailComponent</tt> object. The <tt>createEndpoint()</tt> operation splits the URI into its component parts and uses these parts to create and configure an <tt>Endpoint</tt> object.<br clear="none">
 In the previous paragraph, I mentioned that a <tt>CamelContext</tt> object maintains a mapping from component names to <tt>Component</tt> objects. This raises the question of how this map is populated with named <tt>Component</tt> objects. There are two ways of populating the map. The first way is for application-level code to invoke <tt>CamelContext.addComponent(String componentName, Component component)</tt>. The example below shows a single <tt>MailComponent</tt> object being registered in the map under 3 different names.</p>
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>Component mailComponent = new org.apache.camel.component.mail.MailComponent();<br clear="none">
-myCamelContext.addComponent("pop3", mailComponent);<br clear="none">
-myCamelContext.addComponent("imap", mailComponent);<br clear="none">
-myCamelContext.addComponent("smtp", mailComponent);</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+Component mailComponent = new org.apache.camel.component.mail.MailComponent();
+myCamelContext.addComponent("pop3", mailComponent);
+myCamelContext.addComponent("imap", mailComponent);
+myCamelContext.addComponent("smtp", mailComponent);
+]]></script>
+</div></div>
 <p>The second (and preferred) way to populate the map of named <tt>Component</tt> objects in the <tt>CamelContext</tt> object is to let the <tt>CamelContext</tt> object perform lazy initialization. This approach relies on developers following a convention when they write a class that implements the <tt>Component</tt> interface. I illustrate the convention by an example. Let's assume you write a class called <tt>com.example.myproject.FooComponent</tt> and you want Camel to automatically recognize this by the name "foo". To do this, you have to write a properties file called "META-INF/services/org/apache/camel/component/foo" (without a ".properties" file extension) that has a single entry in it called <tt>class</tt>, the value of which is the fully-scoped name of your class. This is shown below.</p>
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>class=com.example.myproject.FooComponent</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;"><b>META-INF/services/org/apache/camel/component/foo</b></div><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+class=com.example.myproject.FooComponent
+]]></script>
+</div></div>
 <p>If you want Camel to also recognize the class by the name "bar" then you write another properties file in the same directory called "bar" that has the same contents. Once you have written the properties file(s), you create a jar file that contains the <tt>com.example.myproject.FooComponent</tt> class and the properties file(s), and you add this jar file to your CLASSPATH. Then, when application-level code invokes <tt>createEndpoint("foo:...")</tt> on a <tt>CamelContext</tt> object, Camel will find the "foo"" properties file on the CLASSPATH, get the value of the <tt>class</tt> property from that properties file, and use reflection APIs to create an instance of the specified class.<br clear="none">
 As I said in <a shape="rect" href="#BookInOnePage-endpoint">Section 4.1 ("Endpoint")</a>, Camel provides out-of-the-box support for numerous communication technologies. The out-of-the-box support consists of classes that implement the <tt>Component</tt> interface plus properties files that enable a <tt>CamelContext</tt> object to populate its map of named <tt>Component</tt> objects.<br clear="none">
 Earlier in this section I gave the following example of calling <tt>CamelContext.getEndpoint()</tt>.</p>
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>myCamelContext.getEndpoint("pop3://john.smith@mailserv.example.com?password=myPassword");</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+myCamelContext.getEndpoint("pop3://john.smith@mailserv.example.com?password=myPassword");
+]]></script>
+</div></div>
 <p>When I originally gave that example, I said that the parameter to <tt>getEndpoint()</tt> was a URI. I said that because the online Camel documentation and the Camel source code both claim the parameter is a URI. In reality, the parameter is restricted to being a URL. This is because when Camel extracts the component name from the parameter, it looks for the first ":", which is a simplistic algorithm. To understand why, recall from <a shape="rect" href="#BookInOnePage-urluriurniri">Section 4.4 ("The Meaning of URL, URI, URN and IRI")</a> that a URI can be a URL <em>or</em> a URN. Now consider the following calls to <tt>getEndpoint</tt>.</p>
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>myCamelContext.getEndpoint("pop3:...");<br clear="none">
-myCamelContext.getEndpoint("jms:...");<br clear="none">
-myCamelContext.getEndpoint("urn:foo:...");<br clear="none">
-myCamelContext.getEndpoint("urn:bar:...");</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+myCamelContext.getEndpoint("pop3:...");
+myCamelContext.getEndpoint("jms:...");
+myCamelContext.getEndpoint("urn:foo:...");
+myCamelContext.getEndpoint("urn:bar:...");
+]]></script>
+</div></div>
 <p>Camel identifies the components in the above example as "pop3", "jms", "urn" and "urn". It would be more useful if the latter components were identified as "urn:foo" and "urn:bar" or, alternatively, as "foo" and "bar" (that is, by skipping over the "urn:" prefix). So, in practice you must identify an endpoint with a URL (a string of the form "&lt;scheme&gt;:...") rather than with a URN (a string of the form "urn:&lt;scheme&gt;:..."). This lack of proper support for URNs means the you should consider the parameter to <tt>getEndpoint()</tt> as being a URL rather than (as claimed) a URI.</p>
 
 <p><a shape="rect" name="BookInOnePage-messageandexchange"></a></p>
@@ -377,12 +458,14 @@ Application-level programmers rarely acc
 
 <h3><a shape="rect" name="BookInOnePage-Processor"></a>Processor</h3>
 <p>The <tt>Processor</tt> interface represents a class that processes a message. The signature of this interface is shown below.</p>
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>package org.apache.camel;<br clear="none">
-public interface Processor </p>
-<div class="error"><span class="error">Unknown macro: {
+<div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;"><b>Processor</b></div><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+package org.apache.camel;
+public interface Processor {
     void process(Exchange exchange) throws Exception;
-}</span> </div></div>
+}
+]]></script>
+</div></div>
 <p>Notice that the parameter to the <tt>process()</tt> method is an <tt>Exchange</tt> rather than a <tt>Message</tt>. This provides flexibility. For example, an implementation of this method initially might call <tt>exchange.getIn()</tt> to get the input message and process it. If an error occurs during processing then the method can call <tt>exchange.setException()</tt>.<br clear="none">
 An application-level developer might implement the <tt>Processor</tt> interface with a class that executes some business logic. However, there are many classes in the Camel library that implement the <tt>Processor</tt> interface in a way that provides support for a design pattern in the <a shape="rect" href="#BookInOnePage-eipbook">EIP book</a>. For example, <tt>ChoiceProcessor</tt> implements the message router pattern, that is, it uses a cascading if-then-else statement to route a message from an input queue to one of several output queues. Another example is the <tt>FilterProcessor</tt> class which discards messages that do not satisfy a stated <em>predicate</em> (that is, condition).</p>
 
@@ -392,14 +475,21 @@ An application-level developer might imp
 
 <h4><a shape="rect" name="BookInOnePage-IntroductiontoJavaDSL"></a>Introduction to Java DSL</h4>
 <p>For many people, the term "domain-specific language" implies a compiler or interpreter that can process an input file containing keywords and syntax specific to a particular domain. This is <em>not</em> the approach taken by Camel. Camel documentation consistently uses the term "Java DSL" instead of "DSL", but this does not entirely avoid potential confusion. The Camel "Java DSL" is a class library that can be used in a way that looks almost like a DSL, except that it has a bit of Java syntactic baggage. You can see this in the example below. Comments afterwards explain some of the constructs used in the example.</p>
-<div class="error"><span class="error">Unknown macro: {code}</span> 
-<p>RouteBuilder builder = new RouteBuilder() {<br clear="none">
-    public void configure() </p>
-<div class="error"><span class="error">Unknown macro: {
-        from("queue}</span> </div>
-<p>};<br clear="none">
-CamelContext myCamelContext = new DefaultCamelContext();<br clear="none">
-myCamelContext.addRoutes(builder);</p></div>
+<div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;"><b>Example of Camel's "Java DSL"</b></div><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+RouteBuilder builder = new RouteBuilder() {
+    public void configure() {
+        from("queue:a").filter(header("foo").isEqualTo("bar")).to("queue:b");
+        from("queue:c").choice()
+                .when(header("foo").isEqualTo("bar")).to("queue:d")
+                .when(header("foo").isEqualTo("cheese")).to("queue:e")
+                .otherwise().to("queue:f");
+    }
+};
+CamelContext myCamelContext = new DefaultCamelContext();
+myCamelContext.addRoutes(builder);
+]]></script>
+</div></div>
 <p>The first line in the above example creates an object which is an instance of an anonymous subclass of <tt>RouteBuilder</tt> with the specified <tt>configure()</tt> method.<br clear="none">
 The <tt>CamelContext.addRoutes(RouterBuilder builder)</tt> method invokes <tt>builder.setContext(this)</tt> &#8211; so the <tt>RouteBuilder</tt> object knows which <tt>CamelContext</tt> object it is associated with &#8211; and then invokes <tt>builder.configure()</tt>. The body of <tt>configure()</tt> invokes methods such as <tt>from()</tt>, <tt>filter()</tt>, <tt>choice()</tt>, <tt>when()</tt>, <tt>isEqualTo()</tt>, <tt>otherwise()</tt> and <tt>to()</tt>.<br clear="none">
 The <tt>RouteBuilder.from(String uri)</tt> method invokes <tt>getEndpoint(uri)</tt> on the <tt>CamelContext</tt> associated with the <tt>RouteBuilder</tt> object to get the specified <tt>Endpoint</tt> and then puts a <tt>FromBuilder</tt> "wrapper" around this <tt>Endpoint</tt>. The <tt>FromBuilder.filter(Predicate predicate)</tt> method creates a <tt>FilterProcessor</tt> object for the <tt>Predicate</tt> (that is, condition) object built from the <tt>header("foo").isEqualTo("bar")</tt> expression. In this way, these operations incrementally build up a <tt>Route</tt> object (with a <tt>RouteBuilder</tt> wrapper around it) and add it to the <tt>CamelContext</tt> object associated with the <tt>RouteBuilder</tt>.</p>
@@ -444,151 +534,691 @@ However, there is another option that th
 
 <div class="table-wrap">
 <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Component / ArtifactId / URI </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="ahc.html" title="AHC">AHC</a> / camel-ahc
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>ahc:hostname:<span class="error">[port]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> To call external HTTP services using <a shape="rect" class="external-link" href="http://github.com/sonatype/async-http-client" rel="nofollow">Async Http Client</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="amqp.html" title="AMQP">AMQP</a> / camel-amqp
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>amqp:<span class="error">[topic:]</span>destinationName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For Messaging with <a shape="rect" class="external-link" href="http://www.amqp.org/" rel="nofollow">AMQP protocol</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="apns.html" title="APNS">APNS</a> / camel-apns
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>apns:notify<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For sending notifications to Apple iOS devices </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="atom.html" title="Atom">Atom</a> / camel-atom
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>atom:uri</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Working with <a shape="rect" class="external-link" href="http://incubator.apache.org/abdera/">Apache Abdera</a> for atom integration, such as consuming an atom feed. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="avro.html" title="avro">Avro</a> / camel-avro
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>avro:<a shape="rect" href="http://hostname&lt;span class=" error="error">[:port]<span class="error">[?options]</span>" class="external-link" rel="nofollow"&gt;http://hostname<span class="error">[:port]</span><span class="error">[?options]</span></a></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Working with <a shape="rect" class="external-link" href="http://avro.apache.org/">Apache Avro</a> for data serialization. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="aws-cw.html" title="AWS-CW">AWS-CW</a> / <a shape="rect" href="aws.html" title="AWS">camel-aws</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>aws-cw://namespace<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For working with <a shape="rect" class="external-link" href="http://aws.amazon.com/cloudwatch/" rel="nofollow">Amazon's CloudWatch (CW)</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="aws-ddb.html" title="AWS-DDB">AWS-DDB</a> / <a shape="rect" href="aws.html" title="AWS">camel-aws</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>aws-ddb://tableName<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For working with <a shape="rect" class="external-link" href="http://aws.amazon.com/dynamodb/" rel="nofollow">Amazon's DynamoDB (DDB)</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="aws-sdb.html" title="AWS-SDB">AWS-SDB</a> / <a shape="rect" href="aws.html" title="AWS">camel-aws</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>aws-sdb://domainName<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For working with <a shape="rect" class="external-link" href="http://aws.amazon.com/simpledb/" rel="nofollow">Amazon's SimpleDB (SDB)</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="aws-ses.html" title="AWS-SES">AWS-SES</a> / <a shape="rect" href="aws.html" title="AWS">camel-aws</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>aws-ses://from<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For working with <a shape="rect" class="external-link" href="http://aws.amazon.com/ses/" rel="nofollow">Amazon's Simple Email Service (SES)</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="aws-sns.html" title="AWS-SNS">AWS-SNS</a> / <a shape="rect" href="aws.html" title="AWS">camel-aws</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>aws-sns://topicname<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For Messaging with <a shape="rect" class="external-link" href="http://aws.amazon.com/sns/" rel="nofollow">Amazon's Simple Notification Service (SNS)</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="aws-sqs.html" title="AWS-SQS">AWS-SQS</a> / <a shape="rect" href="aws.html" title="AWS">camel-aws</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>aws-sqs://queuename<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For Messaging with <a shape="rect" class="external-link" href="http://aws.amazon.com/sqs/" rel="nofollow">Amazon's Simple Queue Service (SQS)</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="aws-s3.html" title="AWS-S3">AWS-S3</a> / <a shape="rect" href="aws.html" title="AWS">camel-aws</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>aws-s3://bucketname<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For working with <a shape="rect" class="external-link" href="http://aws.amazon.com/s3/" rel="nofollow">Amazon's Simple Storage Service (S3)</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="bean.html" title="Bean">Bean</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>bean:beanName<span class="error">[?method=someMethod]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Uses the <a shape="rect" href="bean-binding.html" title="Bean Binding">Bean Binding</a> to bind message exchanges to beans in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. Is also used for exposing and invoking POJO (Plain Old Java Objects). </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="bean-validation.html" title="Bean Validation">Bean Validation</a> / camel-bean-validator
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>bean-validator:something</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Validates the payload of a message using the Java Validation API (<a shape="rect" class="external-link" href="http://jcp.org/en/jsr/detail?id=303" rel="nofollow">JSR 303</a> and JAXP Validation) and its reference implementation <a shape="rect" class="external-link" href="http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/" rel="nofollow">Hibernate Validator</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="browse.html" title="Browse">Browse</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>browse:someName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Provides a simple <a shape="rect" href="browsableendpoint.html" title="BrowsableEndpoint">BrowsableEndpoint</a> which can be useful for testing, visualisation tools or debugging. The exchanges sent to the endpoint are all available to be browsed. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="cache.html" title="Cache">Cache</a> / camel-cache
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>cache://cachename<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> The cache component facilitates creation of caching endpoints and processors using <a shape="rect" class="external-link" href="http://ehcache.org/" rel="nofollow">EHCache</a> as the cache implementation. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="class.html" title="Class">Class</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>class:className<span class="error">[?method=someMethod]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Uses the <a shape="rect" href="bean-binding.html" title="Bean Binding">Bean Binding</a> to bind message exchanges to beans in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. Is also used for exposing and invoking POJO (Plain Old Java Objects). </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="cmis.html" title="CMIS">CMIS</a> / camel-cmis
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>cmis://cmisServerUrl<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Uses the <a shape="rect" class="external-link" href="http://chemistry.apache.org/java/opencmis.html">Apache Chemistry</a> client API to interface with CMIS supporting CMS </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="cometd.html" title="Cometd">Cometd</a> / camel-cometd
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>cometd://host:port/channelname</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Used to deliver messages using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Cometd+(aka+Bayeux)" rel="nofollow">jetty cometd implementation</a> of the <a shape="rect" class="external-link" href="http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html" rel="nofollow">bayeux protocol</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="context.html" title="Context">Context</a> / camel-context
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>context:camelContextId:localEndpointName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Used to refer to endpoints within a separate CamelContext to provide a simple <a shape="rect" href="context.html" title="Context">black box composition</a> approach so that routes can be combined into a CamelContext and then used as a black box component inside other routes in other CamelContexts </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="controlbus-component.html" title="ControlBus Component">ControlBus</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>controlbus:command<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="controlbus.html" title="ControlBus">ControlBus</a> EIP that allows to send messages to <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a>s for managing and monitoring your Camel applications. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="couchdb.html" title="CouchDB">CouchDB</a> / camel-couchdb
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>couchdb:<a shape="rect" href="http://hostname&lt;span class=" error="error">[:port]/database<span class="error">[?options]</span>" class="external-link" rel="nofollow"&gt;http://hostname<span class="error">[:port]</span>/database<span class="error">[?options]</span></a></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> To integrate with <a shape="rect" class="external-link" href="http://couchdb.apache.org/">Apache CouchDB</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="crypto-digital-signatures.html" title="Crypto (Digital Signatures)">Crypto (Digital Signatures)</a> / camel-crypto
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>crypto:sign:name<span class="error">[?options]</span><br clear="none">
-crypto:verify:name<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Used to sign and verify exchanges using the Signature Service of the Java Cryptographic Extension. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="cxf.html" title="CXF">CXF</a> / camel-cxf
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>cxf:address<span class="error">[?serviceClass=...]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Working with <a shape="rect" class="external-link" href="http://apache.org/cxf/">Apache CXF</a> for web services integration </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="cxf-bean-component.html" title="CXF Bean Component">CXF Bean </a> / camel-cxf
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>cxf:bean name</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Proceess the exchange using a JAX WS or JAX RS annotated bean from the registry. Requires less configuration than the above CXF Component </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="cxfrs.html" title="CXFRS">CXFRS</a> / camel-cxf
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>cxfrs:address<span class="error">[?resourcesClasses=...]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Working with <a shape="rect" class="external-link" href="http://apache.org/cxf/">Apache CXF</a> for REST services integration </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="dataset.html" title="DataSet">DataSet</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>dataset:name</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For load &amp; soak testing the <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/dataset/DataSet.html">DataSet</a> provides a way to create huge numbers of messages for sending to <a shape="rect" href="components.html" title="Components">Components</a> or asserting that they are consumed correctly </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="direct.html" title="Direct">Direct</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>direct:name</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Synchronous call to another endpoint from <b>same</b> CamelContext. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="direct-vm.html" title="Direct-VM">Direct-VM</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>direct-vm:name</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Synchronous call to another endpoint in another CamelContext running in the same JVM. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="dns.html" title="DNS">DNS</a> / camel-dns
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>dns:operation</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> To lookup domain information and run DNS queries using <a shape="rect" class="external-link" href="http://www.xbill.org/dnsjava/" rel="nofollow">DNSJava</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="disruptor.html" title="Disruptor">Disruptor</a> / camel-disruptor 
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>disruptor:name<span class="error">[?option=...]</span><br clear="none">
-disruptor-vm:name<span class="error">[?option=...]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> To provide the implementation of <a shape="rect" href="seda.html" title="SEDA">SEDA</a> which is based on <a shape="rect" class="external-link" href="https://github.com/LMAX-Exchange/disruptor" rel="nofollow">disruptor</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="ejb.html" title="EJB">EJB</a> / camel-ejb
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>ejb:ejbName<span class="error">[?method=someMethod]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Uses the <a shape="rect" href="bean-binding.html" title="Bean Binding">Bean Binding</a> to bind message exchanges to EJBs. It works like the <a shape="rect" href="bean.html" title="Bean">Bean</a> component but just for accessing EJBs. Supports EJB 3.0 onwards. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="elasticsearch.html" title="ElasticSearch">ElasticSearch</a> / camel-elasticsearch
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>elasticsearch://clusterName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For interfacing with an <a shape="rect" class="external-link" href="http://elasticsearch.org" rel="nofollow">ElasticSearch</a> server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="event.html" title="Event">Event</a> / camel-spring
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>event://default<br clear="none">
-spring-event://default</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Working with Spring ApplicationEvents </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="eventadmin.html" title="EventAdmin">EventAdmin</a> / camel-eventadmin
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>eventadmin:topic</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Receiving OSGi EventAdmin events </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="exec.html" title="Exec">Exec</a> / camel-exec
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>exec://executable<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For executing system commands </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="file2.html" title="File2">File</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p><a shape="rect" class="external-link" href="file://nameOfFileOrDirectory" rel="nofollow">file://nameOfFileOrDirectory</a></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sending messages to a file or polling a file or directory. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="flatpack.html" title="Flatpack">Flatpack</a> / camel-flatpack
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>flatpack:<span class="error">[fixed]</span>:configFile</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Processing fixed width or delimited files or messages using the <a shape="rect" class="external-link" href="http://flatpack.sourceforge.net" rel="nofollow">FlatPack library</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="fop.html" title="FOP">FOP</a> / camel-fop
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>fop:outputFormat</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Renders the message into different output formats using <a shape="rect" class="external-link" href="http://xmlgraphics.apache.org/fop/index.html">Apache FOP</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="freemarker.html" title="FreeMarker">FreeMarker</a> / camel-freemarker
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>freemarker:someTemplateResource</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Generates a response using a <a shape="rect" class="external-link" href="http://freemarker.org/" rel="nofollow">FreeMarker</a> template </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> / camel-ftp
-<div class="error"><span class="error">Unknown macro: {code}</span> <p><a shape="rect" href="ftp://host&lt;span class=" error="error">[:port]/fileName" class="external-link" rel="nofollow"&gt;ftp://host<span class="error">[:port]</span>/fileName</a></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sending and receiving files over FTP. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="ftp2.html" title="FTP2">FTPS</a> / camel-ftp
-<div class="error"><span class="error">Unknown macro: {code}</span> <p><a shape="rect" href="ftps://host&lt;span class=" error="error">[:port]/fileName" class="external-link" rel="nofollow"&gt;ftps://host<span class="error">[:port]</span>/fileName</a></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sending and receiving files over FTP Secure (TLS and SSL). </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="gauth.html" title="gauth">GAuth</a> / <a shape="rect" href="gae.html" title="GAE">camel-gae</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>gauth://name<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Used by web applications to implement an <a shape="rect" class="external-link" href="http://code.google.com/apis/accounts/docs/OAuth.html" rel="nofollow">OAuth</a> consumer. See also <a shape="rect" href="gae.html" title="GAE">Camel Components for Google App Engine</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="ghttp.html" title="ghttp">GHttp</a> / <a shape="rect" href="gae.html" title="GAE">camel-gae</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>ghttp://hostname<span class="error">[:port]</span><span class="error">[/path]</span><span class="error">[?options]</span><br clear="none">
-ghttp:///path<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Provides connectivity to the <a shape="rect" class="external-link" href="http://code.google.com/appengine/docs/java/urlfetch/" rel="nofollow">URL fetch service</a> of Google App Engine but can also be used to receive messages from servlets. See also <a shape="rect" href="gae.html" title="GAE">Camel Components for Google App Engine</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="glogin.html" title="glogin">GLogin</a> / <a shape="rect" href="gae.html" title="GAE">camel-gae</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>glogin://hostname<span class="error">[:port]</span><span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Used by Camel applications outside Google App Engine (GAE) for programmatic login to GAE applications. See also <a shape="rect" href="gae.html" title="GAE">Camel Components for Google App Engine</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="gtask.html" title="gtask">GTask</a> / <a shape="rect" href="gae.html" title="GAE">camel-gae</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>gtask://queue-name</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Supports asynchronous message processing on Google App Engine by using the <a shape="rect" class="external-link" href="http://code.google.com/appengine/docs/java/taskqueue/" rel="nofollow">task queueing service</a> as message queue. See also <a shape="rect" href="gae.html" title="GAE">Camel Components for Google App Engine</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="gmail.html" title="gmail">GMail</a> / <a shape="rect" href="gae.html" title="GAE">camel-gae</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>gmail://user@gmail.com<span class="error">[?options]</span><br clear="none">
-gmail://user@googlemail.com<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Supports sending of emails via the <a shape="rect" class="external-link" href="http://code.google.com/appengine/docs/java/mail/" rel="nofollow">mail service</a> of Google App Engine. See also <a shape="rect" href="gae.html" title="GAE">Camel Components for Google App Engine</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="geocoder.html" title="Geocoder">Geocoder</a> / camel-geocoder
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>geocoder:address<span class="error">[?options]</span><br clear="none">
-geocoder:latlng<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Supports looking up geocoders for an address, or reverse lookup geocoders from an address. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="guava-eventbus.html" title="Guava EventBus">Google Guava EventBus</a> / camel-guava-eventbus
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>guava-eventbus:busName<span class="error">[?eventClass=className]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> The <a shape="rect" class="external-link" href="http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html" rel="nofollow">Google Guava EventBus</a> allows publish-subscribe-style communication between components without requiring the components to explicitly register with one another (and thus be aware of each other). This component provides integration bridge between Camel and <a shape="rect" class="external-link" href="http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html" rel="nofollow">Google Guava EventBus</a> infrastructure. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast
 </a> / <a shape="rect" href="hazelcast-component.html" title="Hazelcast Component">camel-hazelcast</a>
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>hazelcast://<span class="error">[type]</span>:cachename<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" class="external-link" href="http://www.hazelcast.com" rel="nofollow">Hazelcast</a> is a data grid entirely implemented in Java (single jar). This component supports map, multimap, seda, queue, set, atomic number and simple cluster support. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="hbase.html" title="hbase">HBase</a> / camel-hbase
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>hbase://table<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For reading/writing from/to an <a shape="rect" class="external-link" href="http://hadoop.apache.org/hbase/">HBase</a> store (Hadoop database) </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> / camel-hdfs
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>hdfs://path<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For reading/writing from/to an <a shape="rect" class="external-link" href="http://hadoop.apache.org/hdfs/">HDFS</a> filesystem </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="hl7.html" title="HL7">HL7</a> / camel-hl7
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>mina:tcp://hostname<span class="error">[:port]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For working with the HL7 MLLP protocol and the HL7 model using the <a shape="rect" class="external-link" href="http://hl7api.sourceforge.net" rel="nofollow">HAPI library</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="http.html" title="HTTP">HTTP</a> / camel-http
-<div class="error"><span class="error">Unknown macro: {code}</span> <p><a shape="rect" href="http://hostname&lt;span class=" error="error">[:port]" class="external-link" rel="nofollow"&gt;http://hostname<span class="error">[:port]</span></a></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For calling out to external HTTP servers using Apache HTTP Client 3.x </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="http4.html" title="HTTP4">HTTP4</a> / camel-http4
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>http4://hostname<span class="error">[:port]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For calling out to external HTTP servers using Apache HTTP Client 4.x </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="ibatis.html" title="iBATIS">iBATIS</a> / camel-ibatis
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>ibatis://statementName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Performs a query, poll, insert, update or delete in a relational database using <a shape="rect" class="external-link" href="http://ibatis.apache.org/">Apache iBATIS</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="mail.html" title="Mail">IMAP</a> / camel-mail
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>imap://hostname<span class="error">[:port]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Receiving email using <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/Internet_Message_Access_Protocol" rel="nofollow">IMAP</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="irc.html" title="IRC">IRC</a> / camel-irc
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>irc:host<span class="error">[:port]</span>/#room</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For IRC communication </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="javaspace.html" title="JavaSpace">JavaSpace</a> / camel-javaspace
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>javaspace:jini://host?spaceName=mySpace?...</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sending and receiving messages through <a shape="rect" class="external-link" href="http://java.sun.com/products/jini/2.1/doc/specs/html/js-spec.html" rel="nofollow">JavaSpace</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jbi.html" title="JBI">JBI</a> / servicemix-camel
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>jbi:serviceName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For JBI integration such as working with <a shape="rect" class="external-link" href="http://servicemix.apache.org">Apache ServiceMix</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jclouds.html" title="jclouds">jclouds</a> / jclouds
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>jclouds:<span class="error">[blobstore]</span>:provider</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For interacting with cloud compute &amp; blobstore service via <a shape="rect" class="external-link" href="http://www.jclouds.org" rel="nofollow">jclouds</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jcr.html" title="JCR">JCR</a> / camel-jcr
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>jcr://user:password@repository/path/to/node</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Storing a message in a JCR compliant repository like <a shape="rect" class="external-link" href="http://jackrabbit.apache.org">Apache Jackrabbit</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jdbc.html" title="JDBC">JDBC</a> / camel-jdbc
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>jdbc:dataSourceName?options</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For performing JDBC queries and operations </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> / camel-jetty
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>jetty:url</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For exposing services over HTTP </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jms.html" title="JMS">JMS</a> / camel-jms
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>jms:<span class="error">[topic:]</span>destinationName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Working with JMS providers </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jmx.html" title="JMX">JMX</a> / camel-jmx
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>jmx://platform?options</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For working with JMX notification listeners </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jpa.html" title="JPA">JPA</a> / camel-jpa
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>jpa://entityName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For using a database as a queue via the JPA specification for working with <a shape="rect" class="external-link" href="http://openjpa.apache.org/">OpenJPA</a>, <a shape="rect" class="external-link" href="http://www.hibernate.org/" rel="nofollow">Hibernate</a> or TopLink </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jsch.html" title="Jsch">Jsch</a> / camel-jsch
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>scp://localhost/destination</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Support for the scp protocol </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jt400.html" title="JT400">JT/400 </a> / camel-jt400
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>jt400://user:pwd@system/&lt;path_to_dtaq&gt;</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For integrating with data queues on an AS/400 (aka System i, IBM i, i5, ...) system </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="kestrel.html" title="Kestrel">Kestrel</a> / camel-kestrel
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>kestrel://<span class="error">[addresslist/]</span>queuename<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For producing to or consuming from <a shape="rect" class="external-link" href="https://github.com/robey/kestrel" rel="nofollow">Kestrel</a> queues </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="krati.html" title="Krati">Krati</a> / camel-krati
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>krati://<span class="error">[path to datastore/]</span><span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For producing to or consuming to <a shape="rect" class="external-link" href="http://sna-projects.com/krati/" rel="nofollow">Krati</a> datastores </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="language.html" title="Language">Language</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>language://languageName<span class="error">[:script]</span><span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Executes <a shape="rect" href="languages.html" title="Languages">Languages</a> scripts </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="ldap.html" title="LDAP">LDAP</a> / camel-ldap
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>ldap:host<span class="error">[:port]</span>?base=...<span class="error">[&amp;scope=&lt;scope&gt;]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Performing searches on LDAP servers (&lt;scope&gt; must be one of object|onelevel|subtree) </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="log.html" title="Log">Log</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>log:loggingCategory<span class="error">[?level=ERROR]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Uses Jakarta Commons Logging to log the message exchange to some underlying logging system like log4j </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="lucene.html" title="Lucene">Lucene</a> / camel-lucene
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>lucene:searcherName:insert<span class="error">[?analyzer=&lt;analyzer&gt;]</span><br clear="none">
-lucene:searcherName:query<span class="error">[?analyzer=&lt;analyzer&gt;]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Uses Apache Lucene to perform Java-based indexing and full text based searches using advanced analysis/tokenization capabilities </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="mail.html" title="Mail">Mail</a> / camel-mail
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>mail://user-info@host:port</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sending and receiving email </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="mina.html" title="MINA">MINA</a> / camel-mina
-<div class="error"><span class="error">Unknown macro: {code}</span> <p><span class="error">[tcp]</span>:host<span class="error">[:port]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Working with <a shape="rect" class="external-link" href="http://mina.apache.org/">Apache MINA</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="mock.html" title="Mock">Mock</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>mock:name</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For testing routes and mediation rules using mocks </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="mongodb.html" title="MongoDB">MongoDB</a> / camel-mongodb
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>mongodb:connection?options</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Interacts with <a shape="rect" class="external-link" href="http://www.mongodb.org/" rel="nofollow">MongoDB</a> databases and collections. Offers producer endpoints to perform CRUD-style operations and more against databases and collections, as well as consumer endpoints to listen on collections and dispatch objects to Camel routes </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="mqtt.html" title="MQTT">MQTT</a> / camel-mqtt
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>mqtt:name</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Component for communicating with <a shape="rect" class="external-link" href="http://mqtt.org" rel="nofollow">MQTT</a> M2M message brokers </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="msv.html" title="MSV">MSV</a> / camel-msv
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>msv:someLocalOrRemoteResource</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Validates the payload of a message using the <a shape="rect" class="external-link" href="https://msv.dev.java.net/" rel="nofollow">MSV Library</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="mustache.html" title="Mustache">Mustache</a> / camel-mustache
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>mustache:someTemplateResource</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Generates a response using a <a shape="rect" class="external-link" href="http://mustache.github.io/" rel="nofollow">Mustache</a> template </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="mvel-component.html" title="MVEL Component">MVEL</a> / camel-mvel
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>mvel:someTemplateResource</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Generates a response using an <a shape="rect" class="external-link" href="http://mvel.codehaus.org/" rel="nofollow">MVEL</a> template </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="mybatis.html" title="MyBatis">MyBatis</a> / camel-mybatis
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>mybatis://statementName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Performs a query, poll, insert, update or delete in a relational database using <a shape="rect" class="external-link" href="http://mybatis.org/" rel="nofollow">MyBatis</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="nagios.html" title="Nagios">Nagios</a> / camel-nagios
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>nagios://host<span class="error">[:port]</span>?options</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sending passive checks to <a shape="rect" class="external-link" href="http://www.nagios.org/" rel="nofollow">Nagios</a> using <a shape="rect" class="external-link" href="http://code.google.com/p/jsendnsca/" rel="nofollow">JSendNSCA</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="netty.html" title="Netty">Netty</a> / camel-netty
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>netty:tcp//host<span class="error">[:port]</span>?options<br clear="none">
-netty:udp//host<span class="error">[:port]</span>?options</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Working with TCP and UDP protocols using Java NIO based capabilities offered by the <a shape="rect" class="external-link" href="http://netty.io/" rel="nofollow">Netty</a> project </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="netty-http.html" title="Netty HTTP">Netty HTTP</a> / camel-netty-http
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>netty-http:http:<span class="error">[port]</span>/context-path?options</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Netty HTTP server and client using the <a shape="rect" class="external-link" href="http://netty.io/" rel="nofollow">Netty</a> project </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="pax-logging.html" title="Pax-Logging">Pax-Logging</a> / camel-paxlogging
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>paxlogging:appender</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Receiving Pax-Logging events in OSGi </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="mail.html" title="Mail">POP</a> / camel-mail
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>pop3://user-info@host:port</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Receiving email using POP3 and JavaMail </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="printer.html" title="Printer">Printer</a> / camel-printer
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>lpr://host:port/path/to/printer<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> The printer component facilitates creation of printer endpoints to local, remote and wireless printers. The endpoints provide the ability to print camel directed payloads when utilized on camel routes. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="properties.html" title="Properties">Properties</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>properties://key<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> The properties component facilitates using property placeholders directly in endpoint uri definitions. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="quartz.html" title="Quartz">Quartz</a> / camel-quartz
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>quartz://groupName/timerName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Provides a scheduled delivery of messages using the <a shape="rect" class="external-link" href="http://www.quartz-scheduler.org/" rel="nofollow">Quartz scheduler</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="quickfix.html" title="Quickfix">Quickfix</a> / camel-quickfix
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>quickfix-server:config file<br clear="none">
-quickfix-client:config-file</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Implementation of the QuickFix for Java engine which allow to send/receive <a shape="rect" class="external-link" href="http://www.fixprotocol.org" rel="nofollow">FIX</a> messages </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="ref.html" title="Ref">Ref</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>ref:name</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Component for lookup of existing endpoints bound in the <a shape="rect" href="registry.html" title="Registry">Registry</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="restlet.html" title="Restlet">Restlet</a> / camel-restlet
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>restlet:restletUrl<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Component for consuming and producing Restful resources using <a shape="rect" class="external-link" href="http://www.restlet.org" rel="nofollow">Restlet</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="rmi.html" title="RMI">RMI</a> / camel-rmi
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>rmi://host<span class="error">[:port]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Working with RMI </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jing.html" title="Jing">RNC</a> / camel-jing
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>rnc:/relativeOrAbsoluteUri</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Validates the payload of a message using <a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="jing.html" title="Jing">RNG</a> / camel-jing
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>rng:/relativeOrAbsoluteUri</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Validates the payload of a message using <a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="routebox.html" title="Routebox">Routebox</a> / camel-routebox
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>routebox:routeboxName<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Facilitates the creation of specialized endpoints that offer encapsulation and a strategy/map based indirection service to a collection of camel routes hosted in an automatically created or user injected camel context </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="rss.html" title="RSS">RSS</a> / camel-rss
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>rss:uri</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Working with <a shape="rect" class="external-link" href="http://rometools.org/" rel="nofollow">ROME</a> for RSS integration, such as consuming an RSS feed. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="sap-netweaver.html" title="SAP NetWeaver">SAP NetWeaver</a> / camel-sap-netweaver
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>sap-netweaver:<a shape="rect" href="https://hostname&lt;span class=" error="error">[:port]" class="external-link" rel="nofollow"&gt;https://hostname<span class="error">[:port]</span></a></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> To integrate with <a shape="rect" class="external-link" href="http://scn.sap.com/docs/DOC-31221" rel="nofollow">SAP NetWeaver Gateway</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="seda.html" title="SEDA">SEDA</a> / camel-core
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>seda:name</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Asynchronous call to another endpoint in the same Camel Context </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="servlet.html" title="SERVLET">SERVLET</a> / camel-servlet
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>servlet:uri</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> For exposing services over HTTP through the servlet which is deployed into the Web container. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="ftp2.html" title="FTP2">SFTP</a> / camel-ftp
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>sftp://host<span class="error">[:port]</span>/fileName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sending and receiving files over SFTP (FTP over SSH). </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="sip.html" title="Sip">Sip</a> / camel-sip
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>sip://user@host<span class="error">[:port]</span>?<span class="error">[options]</span><br clear="none">
-sips://user@host<span class="error">[:port]</span>?<span class="error">[options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Publish/Subscribe communication capability using the Telecom SIP protocol. <a shape="rect" class="external-link" href="http://www.ietf.org/rfc/rfc3903.txt" rel="nofollow">RFC3903 - Session Initiation Protocol (SIP) Extension for Event</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="sjms.html" title="SJMS">SJMS</a> / camel-sjms
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>sjms:<span class="error">[topic:]</span>destinationName?<span class="error">[options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> A ground up implementation of a JMS client </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="mail.html" title="Mail">SMTP</a> / camel-mail
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>smtp://user-info@host<span class="error">[:port]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sending email using SMTP and JavaMail </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="smpp.html" title="SMPP">SMPP</a> / camel-smpp
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>smpp://user-info@host<span class="error">[:port]</span>?options</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> To send and receive SMS using Short Messaging Service Center using the <a shape="rect" class="external-link" href="http://code.google.com/p/jsmpp/" rel="nofollow">JSMPP library</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="snmp.html" title="SNMP">SNMP</a> / camel-snmp
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>snmp://host<span class="error">[:port]</span>?options</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Polling OID values and receiving traps using SNMP via <a shape="rect" class="external-link" href="http://snmp4j.com" rel="nofollow">SNMP4J </a> library </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="solr.html" title="Solr">Solr</a> / camel-solr
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>solr://host<span class="error">[:port]</span>/solr?<span class="error">[options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Uses the <a shape="rect" class="external-link" href="http://wiki.apache.org/solr/Solrj">Solrj</a> client API to interface with an <a shape="rect" class="external-link" href="http://lucene.apache.org/solr/">Apache Lucene Solr</a> server </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="springbatch.html" title="SpringBatch">SpringBatch</a> / camel-spring-batch
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>spring-batch:job<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> To bridge Camel and <a shape="rect" class="external-link" href="http://www.springsource.org/spring-batch" rel="nofollow">Spring Batch</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="springintegration.html" title="SpringIntegration">SpringIntegration</a> / camel-spring-integration
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>spring-integration:defaultChannelName</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> The bridge component of Camel and <a shape="rect" class="external-link" href="http://www.springframework.org/spring-integration" rel="nofollow">Spring Integration</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="spring-ldap.html" title="Spring LDAP">Spring LDAP</a> / camel-spring-ldap
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>spring-ldap:spring-ldap-template-bean?options</p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Camel wrapper for <a shape="rect" class="external-link" href="http://www.springsource.org/ldap" rel="nofollow">Spring LDAP</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="spring-redis.html" title="Spring Redis">Spring Redis</a> / camel-spring-redis
-<div class="error"><span class="error">Unknown macro: {code}</span> <p>spring-redis:restletUrl<span class="error">[?options]</span></p></div> </td><td colspan="1" rowspan="1" class="confluenceTd"> Component for consuming and producing from Redis key-value store <a shape="rect" class="external-link" href="http://redis.io" rel="nofollow">Redis</a> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="spring-web-services.html" title="Spring Web Services">Spring Web Services</a> / camel-spring-ws

[... 47003 lines stripped ...]


Mime
View raw message