You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2018/11/29 08:26:59 UTC
svn commit: r1037379 [20/20] - in /websites/production/camel/content: ./
2018/11/29/ cache/
Modified: websites/production/camel/content/spring-remoting.html
==============================================================================
--- websites/production/camel/content/spring-remoting.html (original)
+++ websites/production/camel/content/spring-remoting.html Thu Nov 29 08:26:57 2018
@@ -159,7 +159,7 @@ Error rendering macro 'code': Invalid va
<p>For more details see <a shape="rect" href="using-exchange-pattern-annotations.html">Using Exchange Pattern Annotations</a></p>
-<h2 id="SpringRemoting-BeanBinding">Bean Binding</h2><p>Bean Binding in Camel defines both which methods are invoked and also how the <a shape="rect" href="message.html">Message</a> is converted into the parameters of the method when it is invoked.</p><h3 id="SpringRemoting-Choosingthemethodtoinvoke">Choosing the method to invoke</h3><p>The binding of a Camel <a shape="rect" href="message.html">Message</a> to a bean method call can occur in different ways, in the following order of importance:</p><ul><li>if the message contains the header <strong>CamelBeanMethodName</strong> then that method is invoked, converting the body to the type of the method's argument.<ul><li>From <strong>Camel 2.8</strong> onwards you can qualify parameter types to select exactly which method to use among overloads with the same name (see below for more details).</li><li>From <strong>Camel 2.9</strong> onwards you can specify parameter values directly in the method option (see below for more details).</li><
/ul></li><li>you can explicitly specify the method name in the <a shape="rect" href="dsl.html">DSL</a> or when using <a shape="rect" href="pojo-consuming.html">POJO Consuming</a> or <a shape="rect" href="pojo-producing.html">POJO Producing</a></li><li>if the bean has a method marked with the <code>@Handler</code> annotation, then that method is selected</li><li>if the bean can be converted to a <a shape="rect" href="processor.html">Processor</a> using the <a shape="rect" href="type-converter.html">Type Converter</a> mechanism, then this is used to process the message. The <a shape="rect" href="activemq.html">ActiveMQ</a> component uses this mechanism to allow any JMS MessageListener to be invoked directly by Camel without having to write any integration glue code. You can use the same mechanism to integrate Camel into any other messaging/remoting frameworks.</li><li>if the body of the message can be converted to a <a shape="rect" class="external-link" href="http://camel.apache.org/m
aven/current/camel-core/apidocs/org/apache/camel/component/bean/BeanInvocation.html">BeanInvocation</a> (the default payload used by the <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/bean/ProxyHelper.html">ProxyHelper</a>) component - then that is used to invoke the method and pass its arguments</li><li>otherwise the type of the body is used to find a matching method; an error is thrown if a single method cannot be chosen unambiguously.</li><li>you can also use Exchange as the parameter itself, but then the return type must be void.</li><li>if the bean class is private (or package-private), interface methods will be preferred (from <strong>Camel 2.9</strong> onwards) since Camel can't invoke class methods on such beans</li></ul><p>In cases where Camel cannot choose a method to invoke, an <code>AmbiguousMethodCallException</code> is thrown.</p><p>By default the return value is set on the outbound messag
e body. </p><h3 id="SpringRemoting-Asynchronousprocessing">Asynchronous processing</h3><p>From <strong>Camel 2.18</strong> onwards you can return a CompletionStage implementation (e.g. a CompletableFuture) to implement asynchronous processing.</p><p>Please be sure to properly complete the CompletionStage with the result or exception, including any timeout handling. Exchange processing would wait for completion and would not impose any timeouts automatically. It's extremely useful to monitor <a shape="rect" class="external-link" href="https://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/InflightRepository.html">Inflight repository</a> for any hanging messages.</p><p>Note that completing with "null" won't set outbody message body to null, but would keep message intact. This is useful to support methods that don't modify exchange and return CompletableFuture<Void>. To set body to null, just add Exchange method parameter and directly m
odify exchange messages.</p><p>Examples:</p><p>Simple asynchronous processor, modifying message body.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h2 id="SpringRemoting-BeanBinding">Bean Binding</h2><p>Bean Binding in Camel defines both which methods are invoked and also how the <a shape="rect" href="message.html">Message</a> is converted into the parameters of the method when it is invoked.</p><h3 id="SpringRemoting-Choosingthemethodtoinvoke">Choosing the method to invoke</h3><p>The binding of a Camel <a shape="rect" href="message.html">Message</a> to a bean method call can occur in different ways, in the following order of importance:</p><ul><li>if the message contains the header <strong>CamelBeanMethodName</strong> then that method is invoked, converting the body to the type of the method's argument.<ul><li>From <strong>Camel 2.8</strong> onwards you can qualify parameter types to select exactly which method to use among overloads with the same name (see below for more details).</li><li>From <strong>Camel 2.9</strong> onwards you can specif
y parameter values directly in the method option (see below for more details).</li></ul></li><li>you can explicitly specify the method name in the <a shape="rect" href="dsl.html">DSL</a> or when using <a shape="rect" href="pojo-consuming.html">POJO Consuming</a> or <a shape="rect" href="pojo-producing.html">POJO Producing</a></li><li>if the bean has a method marked with the <code>@Handler</code> annotation, then that method is selected</li><li>if the bean can be converted to a <a shape="rect" href="processor.html">Processor</a> using the <a shape="rect" href="type-converter.html">Type Converter</a> mechanism, then this is used to process the message. The <a shape="rect" href="activemq.html">ActiveMQ</a> component uses this mechanism to allow any JMS MessageListener to be invoked directly by Camel without having to write any integration glue code. You can use the same mechanism to integrate Camel into any other messaging/remoting frameworks.</li><li>if the body of the message can be
converted to a <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/bean/BeanInvocation.html">BeanInvocation</a> (the default payload used by the <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/bean/ProxyHelper.html">ProxyHelper</a>) component - then that is used to invoke the method and pass its arguments</li><li>otherwise the type of the body is used to find a matching method; an error is thrown if a single method cannot be chosen unambiguously.</li><li>you can also use Exchange as the parameter itself, but then the return type must be void.</li><li>if the bean class is private (or package-private), interface methods will be preferred (from <strong>Camel 2.9</strong> onwards) since Camel can't invoke class methods on such beans</li></ul><p>In cases where Camel cannot choose a method to invoke, an <code>AmbiguousMethodCallExcepti
on</code> is thrown.</p><p>By default the return value is set on the outbound message body. </p><h3 id="SpringRemoting-Asynchronousprocessing">Asynchronous processing</h3><p>From <strong>Camel 2.18</strong> onwards you can return a CompletionStage implementation (e.g. a CompletableFuture) to implement asynchronous processing.</p><p>Please be sure to properly complete the CompletionStage with the result or exception, including any timeout handling. Exchange processing would wait for completion and would not impose any timeouts automatically. It's extremely useful to monitor <a shape="rect" class="external-link" href="https://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/InflightRepository.html">Inflight repository</a> for any hanging messages.</p><p>Note that completing with "null" won't set outbody message body to null, but would keep message intact. This is useful to support methods that don't modify exchange and return CompletableFuture
<Void>. To set body to null, just add Exchange method parameter and directly modify exchange messages.</p><p>Examples:</p><p>Simple asynchronous processor, modifying message body.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">public CompletableFuture<String> doSomethingAsync(String body)</pre>
</div></div><p><br clear="none">Composite processor that do not modify exchange</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default"> public CompletableFuture<Void> doSomethingAsync(String body) {
@@ -233,7 +233,7 @@ Error rendering macro 'code': Invalid va
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">.bean(OrderService.class, "doSomething(com.foo.MyOrder)")</pre>
</div></div><p><br clear="none">Camel currently only supports either specifying parameter binding or type per parameter in the method name option. You <strong>cannot</strong> specify both at the same time, such as</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default"> doSomething(com.foo.MyOrder ${body}, boolean ${header.high})</pre>
-</div></div><p>This may change in the future.</p></div>
+</div></div><p>This may change in the future.</p></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/spring-web-services.html
==============================================================================
--- websites/production/camel/content/spring-web-services.html (original)
+++ websites/production/camel/content/spring-web-services.html Thu Nov 29 08:26:57 2018
@@ -276,8 +276,8 @@ from("direct:example").marshal(jaxb).to(
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("spring-ws:rootqname:{http://example.com/}GetFoo?endpointMapping=#endpointMapping").unmarshal(jaxb)
.to("mock:example").marshal(jaxb);
</pre>
-</div></div><p></p><h3 id="SpringWebServices-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+</div></div><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="SpringWebServices-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/sql-stored-procedure.html
==============================================================================
--- websites/production/camel/content/sql-stored-procedure.html (original)
+++ websites/production/camel/content/sql-stored-procedure.html Thu Nov 29 08:26:57 2018
@@ -114,8 +114,8 @@
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default"><to uri="sql-stored:SUBNUMBERS(INTEGER ${headers.num1},INTEGER ${headers.num2},OUT INTEGER resultofsub)"/></pre>
</div></div><p>The arguments is declared by a type and then the mapping to the Camel message using simple expression. So in this example the first two parameters are IN values that are INTEGER type, that maps to the message headers. The last parameter is the OUT value, also an INTEGER type.</p><p>In SQL term the stored procedure could be declared as:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">CREATE PROCEDURE SUBNUMBERS(VALUE1 INTEGER, VALUE2 INTEGER,OUT RESULT INTEGER)</pre>
-</div></div><p> </p><p></p><h3 id="SQLStoredProcedure-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul><ul class="alternate"><li><a shape="rect" href="sql-component.html">SQL Component</a></li></ul></div>
+</div></div><p> </p><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="SQLStoredProcedure-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div><ul class="alternate"><li><a shape="rect" href="sql-component.html">SQL Component</a></li></ul></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/ssh.html
==============================================================================
--- websites/production/camel/content/ssh.html (original)
+++ websites/production/camel/content/ssh.html Thu Nov 29 08:26:57 2018
@@ -206,8 +206,8 @@ from("ssh://scott@localhost:8101?certRes
<p>See the <code>examples/camel-example-ssh</code> and <code>examples/camel-example-ssh-security</code> in the Camel distribution.</p>
-<h3 id="SSH-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="SSH-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/stax.html
==============================================================================
--- websites/production/camel/content/stax.html (original)
+++ websites/production/camel/content/stax.html Thu Nov 29 08:26:57 2018
@@ -281,8 +281,8 @@ Error rendering macro 'code': Invalid va
</pre>
-<h3 id="StAX-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="StAX-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/stomp.html
==============================================================================
--- websites/production/camel/content/stomp.html (original)
+++ websites/production/camel/content/stomp.html Thu Nov 29 08:26:57 2018
@@ -108,17 +108,17 @@
</div></div><p>Consuming messages:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("stomp:queue:test").transform(body().convertToString()).to("mock:result")
</pre>
-</div></div><p></p><h2 id="Stomp-Endpoints">Endpoints</h2>
+</div></div><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h2 id="Stomp-Endpoints">Endpoints</h2>
<p><span class="conf-macro output-inline" data-hasbody="true" data-macro-name="excerpt"></span></p><p>Camel supports the <a shape="rect" href="message-endpoint.html">Message Endpoint</a> pattern using the <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html">Endpoint</a> interface. Endpoints are usually created by a <a shape="rect" href="component.html">Component</a> and Endpoints are usually referred to in the <a shape="rect" href="dsl.html">DSL</a> via their <a shape="rect" href="uris.html">URIs</a>. </p>
<p>From an Endpoint you can use the following methods</p>
<ul><li><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html#createProducer()">createProducer()</a> will create a <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Producer.html">Producer</a> for sending message exchanges to the endpoint</li><li><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html#createConsumer(org.apache.camel.Processor)">createConsumer()</a> implements the <a shape="rect" href="event-driven-consumer.html">Event Driven Consumer</a> pattern for consuming message exchanges from the endpoint via a <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html">Processor</a> when creating a <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-
core/apidocs/org/apache/camel/Consumer.html">Consumer</a></li><li><a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html#createPollingConsumer()">createPollingConsumer()</a> implements the <a shape="rect" href="polling-consumer.html">Polling Consumer</a> pattern for consuming message exchanges from the endpoint via a <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/PollingConsumer.html">PollingConsumer</a></li></ul>
-
+<p></p>
<h3 id="Stomp-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="message-endpoint.html">Message Endpoint</a> pattern</li><li><a shape="rect" href="uris.html">URIs</a></li><li><a shape="rect" href="writing-components.html">Writing Components</a></li></ul></div>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="message-endpoint.html">Message Endpoint</a> pattern</li><li><a shape="rect" href="uris.html">URIs</a></li><li><a shape="rect" href="writing-components.html">Writing Components</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/stub.html
==============================================================================
--- websites/production/camel/content/stub.html (original)
+++ websites/production/camel/content/stub.html Thu Nov 29 08:26:57 2018
@@ -112,8 +112,8 @@ stub:someUri
<ul><li>stub:smtp://somehost.foo.com?user=whatnot&something=else</li><li>stub:<a shape="rect" class="external-link" href="http://somehost.bar.com/something" rel="nofollow">http://somehost.bar.com/something</a></li></ul>
-<h3 id="Stub-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="Stub-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/syslog.html
==============================================================================
--- websites/production/camel/content/syslog.html (original)
+++ websites/production/camel/content/syslog.html Thu Nov 29 08:26:57 2018
@@ -140,8 +140,8 @@
</camelContext>
</pre>
-</div></div><p></p><h3 id="Syslog-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+</div></div><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="Syslog-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/test.html
==============================================================================
--- websites/production/camel/content/test.html (original)
+++ websites/production/camel/content/test.html Thu Nov 29 08:26:57 2018
@@ -88,7 +88,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Test-TestComponent">Test Component</h2><p><a shape="rect" href="testing.html">Testing</a> of distributed and asynchronous processing is notoriously difficult. The <a shape="rect" href="mock.html">Mock</a>, <a shape="rect" href="test.html">Test</a> and <a shape="rect" href="dataset.html">DataSet</a> endpoints work great with the <a shape="rect" href="testing.html">Camel Testing Framework</a> to simplify your unit and integration testing using <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a> and Camel's large range of <a shape="rect" href="components.html">Components</a> together with the powerful <a shape="rect" href="bean-integration.html">Bean Integration</a>.</p><p>The <strong><code>test</code></strong> component extends the <a shape="rect" href="mock.html">Mock</a> component to support pulling messages from another endpoint on startup to set the expected message bodies on the underlying <
a shape="rect" href="mock.html">Mock</a> endpoint. That is, you use the test endpoint in a route and messages arriving on it will be implicitly compared to some expected messages extracted from some other location.</p><p>So you can use, for example, an expected set of message bodies as files. This will then set up a properly configured <a shape="rect" href="mock.html">Mock</a> endpoint, which is only valid if the received messages match the number of expected messages and their message payloads are equal.</p><p>Maven users will need to add the following dependency to their <strong><code>pom.xml</code></strong> for this component when using <strong>Camel 2.8</strong> or older:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="Test-TestComponent">Test Component</h2><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><a shape="rect" href="testing.html">Testing</a> of distributed and asynchronous processing is notoriously difficult. The <a shape="rect" href="mock.html">Mock</a>, <a shape="rect" href="test.html">Test</a> and <a shape="rect" href="dataset.html">DataSet</a> endpoints work great with the <a shape="rect" href="testing.html">Camel Testing Framework</a> to simplify your unit and integration testing using <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a> and Camel's large range of <a shape="rect" href="components.html">Components</a> together with the powerful <a shape="rect" href="bean-integration.html">Bean Integration</a>.</div><p>The <strong><code>test</code></strong> component extends the <a shape="rect" href="mock.html">Mock</a> component to support pulling messag
es from another endpoint on startup to set the expected message bodies on the underlying <a shape="rect" href="mock.html">Mock</a> endpoint. That is, you use the test endpoint in a route and messages arriving on it will be implicitly compared to some expected messages extracted from some other location.</p><p>So you can use, for example, an expected set of message bodies as files. This will then set up a properly configured <a shape="rect" href="mock.html">Mock</a> endpoint, which is only valid if the received messages match the number of expected messages and their message payloads are equal.</p><p>Maven users will need to add the following dependency to their <strong><code>pom.xml</code></strong> for this component when using <strong>Camel 2.8</strong> or older:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default"><dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-spring</artifactId>
@@ -106,8 +106,8 @@
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("seda:someEndpoint")
.to("test:file://data/expectedOutput?noop=true");
</pre>
-</div></div><p>If your test then invokes the <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/mock/MockEndpoint.html#assertIsSatisfied(org.apache.camel.CamelContext)">MockEndpoint.assertIsSatisfied(camelContext) method</a>, your test case will perform the necessary assertions.</p><p>To see how you can set other expectations on the test endpoint, see the <a shape="rect" href="mock.html">Mock</a> component.</p><p></p><h3 id="Test-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul><ul><li><a shape="rect" href="spring-testing.html">Spring Testing</a></li></ul></div>
+</div></div><p>If your test then invokes the <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/mock/MockEndpoint.html#assertIsSatisfied(org.apache.camel.CamelContext)">MockEndpoint.assertIsSatisfied(camelContext) method</a>, your test case will perform the necessary assertions.</p><p>To see how you can set other expectations on the test endpoint, see the <a shape="rect" href="mock.html">Mock</a> component.</p><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="Test-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div><ul><li><a shape="rect" href="spring-testing.html">Spring Testing</a></li></ul></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/timer.html
==============================================================================
--- websites/production/camel/content/timer.html (original)
+++ websites/production/camel/content/timer.html Thu Nov 29 08:26:57 2018
@@ -120,8 +120,8 @@
<to uri="bean:myBean?method=someMethodName"/>
</route>
</pre>
-</div></div><p></p><h3 id="Timer-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul><ul><li><a shape="rect" href="quartz.html">Quartz</a></li></ul></div>
+</div></div><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="Timer-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div><ul><li><a shape="rect" href="quartz.html">Quartz</a></li></ul></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/transport.html
==============================================================================
--- websites/production/camel/content/transport.html (original)
+++ websites/production/camel/content/transport.html Thu Nov 29 08:26:57 2018
@@ -93,7 +93,7 @@
<p>Apache Camel supports a number of different plugable componets for talking to different transports. The transports is implement as Camel components.</p>
-<h3 id="Transport-ComponentsIncluded">Components Included</h3><p>Camel includes the following <a shape="rect" href="component.html">Component</a> implementations via <a shape="rect" href="uris.html">URIs</a>.</p><div class="confluence-information-macro confluence-information-macro-tip conf-macro output-block" data-hasbody="true" data-macro-name="tip"><p class="title">important</p><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>Make sure to read <a shape="rect" href="how-do-i-configure-endpoints.html">How Do I Configure Endpoints?</a> to learn more about configuring endpoints. For example how to refer to beans in the <a shape="rect" href="registry.html">Registry</a> or how to use raw values for password options, and using <a shape="rect" href="using-propertyplaceholder.html">property placeholders</a> etc.</p></div></div><p></p><div class="table-wrap"><table class="confluenceTable"><
tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Component / ArtifactId / URI</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="ahc.html">AHC</a> / <code>camel-ahc</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="Transport-ComponentsIncluded">Components Included</h3><p>Camel includes the following <a shape="rect" href="component.html">Component</a> implementations via <a shape="rect" href="uris.html">URIs</a>.</p><div class="confluence-information-macro confluence-information-macro-tip conf-macro output-block" data-hasbody="true" data-macro-name="tip"><p class="title">important</p><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>Make sure to read <a shape="rect" href="how-do-i-configure-endpoints.html">How Do I Configure Endpoints?</a> to learn more about configuring endpoints. For example how to refer to beans in the <a shape="rect" href="registry.html">Registry</a> or how to use raw values for password options, and using <a shape="rect" href="using-propertyplaceholder.html">property placeholders</a>
etc.</p></div></div><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Component / ArtifactId / URI</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="ahc.html">AHC</a> / <code>camel-ahc</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">ahc:http[s]://hostName[:port][/resourceUri][?options]
</pre>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To call external HTTP services using <a shape="rect" class="external-link" href="https://github.com/AsyncHttpClient/async-http-client" rel="nofollow">Async Http Client</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="ahc-ws.html">AHC-WS</a> <span> / <code>camel-ahc-ws</code></span></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -690,7 +690,7 @@ flink:datastream[?options]</pre>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Allows you to interact with the <a shape="rect" class="external-link" href="http://yammer.com" rel="nofollow">Yammer</a> enterprise social network</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="zookeeper.html">Zookeeper</a> / <code>camel-zookeeper</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">zookeeper://zookeeperServer[:port][/path][?options]
</pre>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Working with <a shape="rect" class="external-link" href="http://hadoop.apache.org/zookeeper/">ZooKeeper</a> cluster(s)</p></td></tr></tbody></table></div><p> </p><div><span style="white-space: pre-wrap;"> <br clear="none"> </span></div><div><span style="white-space: pre-wrap;"> <br clear="none"> </span></div><div><span style="white-space: pre-wrap;"> <br clear="none"> <br clear="none"> </span></div><h3 id="Transport-ExternalComponents">External Components</h3><p>The following components are not part of the standard Apache Camel distribution and are available under a variety of licenses but can be used to extend Camel's functionality.</p><p></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Component / ArtifactId / URI</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>License</p></th><th colspan="1" rowspan="1" class="confluenceTh"
><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="activemq.html">ActiveMQ</a> / <code>activemq-camel</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Working with <a shape="rect" class="external-link" href="http://hadoop.apache.org/zookeeper/">ZooKeeper</a> cluster(s)</p></td></tr></tbody></table></div><p> </p><div><span style="white-space: pre-wrap;"> <br clear="none"> </span></div><div><span style="white-space: pre-wrap;"> <br clear="none"> </span></div><div><span style="white-space: pre-wrap;"> <br clear="none"> <br clear="none"> </span></div></div><p></p><h3 id="Transport-ExternalComponents">External Components</h3><p>The following components are not part of the standard Apache Camel distribution and are available under a variety of licenses but can be used to extend Camel's functionality.</p><p></p><div class="table-wrap conf-macro output-block" data-hasbody="false" data-macro-name="include"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Component / ArtifactId / URI</p></th><th colspan="1" rowspan="1" clas
s="confluenceTh"><p>License</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="activemq.html">ActiveMQ</a> / <code>activemq-camel</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: xml; gutter: false; theme: Default" data-theme="Default">activemq:[queue|topic:]destinationName</pre>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For JMS Messaging with <a shape="rect" class="external-link" href="http://activemq.apache.org/" title="The most popular and powerful open source message broker">Apache ActiveMQ.</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/broker-camel-component.html">ActiveMQ Broker</a> / <code>activemq-camel</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: text; gutter: false; theme: Default" data-theme="Default">broker:[queue|topic:]destinationName</pre>
@@ -771,7 +771,7 @@ flink:datastream[?options]</pre>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Camel <a shape="rect" class="external-link" href="http://webcam-capture.sarxos.pl/" rel="nofollow">Webcam</a> component can be used to capture still images and detect motion.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="zeromq.html">ZeroMQ</a> / <code>camel-zeromq</code> / <a shape="rect" class="external-link" href="http://code.google.com/p/camel-extra/" rel="nofollow">camel-extra</a></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">zeromq:(tcp|ipc)://hostname:port
</pre>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>LGPL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The ZeroMQ component allows you to consumer or produce messages using <a shape="rect" class="external-link" href="http://zeromq.org" rel="nofollow">ZeroMQ</a>.</p></td></tr></tbody></table></div><h3 id="Transport-SeeAlso">See Also</h3><ul><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="uris.html">URIs</a></li><li><a shape="rect" href="writing-components.html">Writing Components</a></li><li><a shape="rect" href="how-do-i-add-a-component.html">How do I add a component</a></li><li><a shape="rect" href="how-do-i-configure-endpoints.html">How Do I Configure Endpoints?</a></li><li><a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a></li></ul></div>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>LGPL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The ZeroMQ component allows you to consumer or produce messages using <a shape="rect" class="external-link" href="http://zeromq.org" rel="nofollow">ZeroMQ</a>.</p></td></tr></tbody></table></div><p></p><h3 id="Transport-SeeAlso">See Also</h3><ul><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="uris.html">URIs</a></li><li><a shape="rect" href="writing-components.html">Writing Components</a></li><li><a shape="rect" href="how-do-i-add-a-component.html">How do I add a component</a></li><li><a shape="rect" href="how-do-i-configure-endpoints.html">How Do I Configure Endpoints?</a></li><li><a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/twitter.html
==============================================================================
--- websites/production/camel/content/twitter.html (original)
+++ websites/production/camel/content/twitter.html Thu Nov 29 08:26:57 2018
@@ -120,8 +120,8 @@
.setHeader("CamelTwitterKeywords", header("bar"))
.to("twitter://search?consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]");
</pre>
-</div></div><h3 id="Twitter-Example">Example</h3><p>See also the <a shape="rect" href="twitter-websocket-example.html">Twitter Websocket Example</a>.</p><p></p><h3 id="Twitter-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul><ul class="alternate"><li><a shape="rect" href="twitter-websocket-example.html">Twitter Websocket Example</a></li></ul></div>
+</div></div><h3 id="Twitter-Example">Example</h3><p>See also the <a shape="rect" href="twitter-websocket-example.html">Twitter Websocket Example</a>.</p><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="Twitter-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div><ul class="alternate"><li><a shape="rect" href="twitter-websocket-example.html">Twitter Websocket Example</a></li></ul></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/undertow.html
==============================================================================
--- websites/production/camel/content/undertow.html (original)
+++ websites/production/camel/content/undertow.html Thu Nov 29 08:26:57 2018
@@ -119,8 +119,8 @@
<from uri="undertow:http://localhost:8080/myapp/myservice"/>
<to uri="bean:myBean"/>
</route></pre>
-</div></div><div class="confluence-information-macro confluence-information-macro-note conf-macro output-block" data-hasbody="true" data-macro-name="note"><p class="title">Usage of localhost</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>When you specify <code>localhost</code> in a URL, Camel exposes the endpoint only on the local TCP/IP network interface, so it cannot be accessed from outside the machine it operates on.</p><p>If you need to expose a Jetty endpoint on a specific network interface, the numerical IP address of this interface should be used as the host. If you need to expose a Jetty endpoint on all network interfaces, the <code>0.0.0.0</code> address should be used.</p></div></div><div class="confluence-information-macro confluence-information-macro-tip conf-macro output-block" data-hasbody="true" data-macro-name="tip"><span class="aui-icon aui-icon-small aui-icon
font-approve confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>To listen across an entire URI prefix, see <a shape="rect" href="how-do-i-let-jetty-match-wildcards.html">How do I let Jetty match wildcards</a>.</p></div></div><div class="confluence-information-macro confluence-information-macro-tip conf-macro output-block" data-hasbody="true" data-macro-name="tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>If you actually want to expose routes by HTTP and already have a Servlet, you should instead refer to the <a shape="rect" href="https://cwiki.apache.org/confluence/display/CXF20DOC/Servlet+Transport">Servlet Transport</a>.</p></div></div><p> </p><p> </p><p></p><h3 id="Undertow-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul><ul class="alternate"><li><a shape="rect" href="jetty.html">Jetty</a></li><li><a shape="rect" href="http.html">HTTP</a></li></ul></div>
+</div></div><div class="confluence-information-macro confluence-information-macro-note conf-macro output-block" data-hasbody="true" data-macro-name="note"><p class="title">Usage of localhost</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>When you specify <code>localhost</code> in a URL, Camel exposes the endpoint only on the local TCP/IP network interface, so it cannot be accessed from outside the machine it operates on.</p><p>If you need to expose a Jetty endpoint on a specific network interface, the numerical IP address of this interface should be used as the host. If you need to expose a Jetty endpoint on all network interfaces, the <code>0.0.0.0</code> address should be used.</p></div></div><div class="confluence-information-macro confluence-information-macro-tip conf-macro output-block" data-hasbody="true" data-macro-name="tip"><span class="aui-icon aui-icon-small aui-icon
font-approve confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>To listen across an entire URI prefix, see <a shape="rect" href="how-do-i-let-jetty-match-wildcards.html">How do I let Jetty match wildcards</a>.</p></div></div><div class="confluence-information-macro confluence-information-macro-tip conf-macro output-block" data-hasbody="true" data-macro-name="tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>If you actually want to expose routes by HTTP and already have a Servlet, you should instead refer to the <a shape="rect" href="https://cwiki.apache.org/confluence/display/CXF20DOC/Servlet+Transport">Servlet Transport</a>.</p></div></div><p> </p><p> </p><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="Undertow-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div><ul class="alternate"><li><a shape="rect" href="jetty.html">Jetty</a></li><li><a shape="rect" href="http.html">HTTP</a></li></ul></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/uris.html
==============================================================================
--- websites/production/camel/content/uris.html (original)
+++ websites/production/camel/content/uris.html Thu Nov 29 08:26:57 2018
@@ -98,7 +98,7 @@
<h3 id="URIs-CurrentSupportedURIs">Current Supported URIs</h3>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Component / ArtifactId / URI</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="ahc.html">AHC</a> / <code>camel-ahc</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Component / ArtifactId / URI</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="ahc.html">AHC</a> / <code>camel-ahc</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">ahc:http[s]://hostName[:port][/resourceUri][?options]
</pre>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To call external HTTP services using <a shape="rect" class="external-link" href="https://github.com/AsyncHttpClient/async-http-client" rel="nofollow">Async Http Client</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="ahc-ws.html">AHC-WS</a> <span> / <code>camel-ahc-ws</code></span></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -695,14 +695,14 @@ flink:datastream[?options]</pre>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Allows you to interact with the <a shape="rect" class="external-link" href="http://yammer.com" rel="nofollow">Yammer</a> enterprise social network</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="zookeeper.html">Zookeeper</a> / <code>camel-zookeeper</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">zookeeper://zookeeperServer[:port][/path][?options]
</pre>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Working with <a shape="rect" class="external-link" href="http://hadoop.apache.org/zookeeper/">ZooKeeper</a> cluster(s)</p></td></tr></tbody></table></div><p> </p><div><span style="white-space: pre-wrap;"> <br clear="none"> </span></div><div><span style="white-space: pre-wrap;"> <br clear="none"> </span></div><div><span style="white-space: pre-wrap;"> <br clear="none"> <br clear="none"> </span></div>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Working with <a shape="rect" class="external-link" href="http://hadoop.apache.org/zookeeper/">ZooKeeper</a> cluster(s)</p></td></tr></tbody></table></div><p> </p><div><span style="white-space: pre-wrap;"> <br clear="none"> </span></div><div><span style="white-space: pre-wrap;"> <br clear="none"> </span></div><div><span style="white-space: pre-wrap;"> <br clear="none"> <br clear="none"> </span></div></div>
<h3 id="URIs-URI'sforexternalcomponents">URI's for external components</h3>
<p>Other projects and companies have also created Camel components to integrate additional functionality into Camel. These components may be provided under licenses that are not compatible with the Apache License, use libraries that are not compatible, etc... These components are not supported by the Camel team, but we provide links here to help users find the additional functionality.</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Component / ArtifactId / URI</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>License</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="activemq.html">ActiveMQ</a> / <code>activemq-camel</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="table-wrap conf-macro output-block" data-hasbody="false" data-macro-name="include"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Component / ArtifactId / URI</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>License</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="activemq.html">ActiveMQ</a> / <code>activemq-camel</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: xml; gutter: false; theme: Default" data-theme="Default">activemq:[queue|topic:]destinationName</pre>
</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For JMS Messaging with <a shape="rect" class="external-link" href="http://activemq.apache.org/" title="The most popular and powerful open source message broker">Apache ActiveMQ.</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/broker-camel-component.html">ActiveMQ Broker</a> / <code>activemq-camel</code></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: text; gutter: false; theme: Default" data-theme="Default">broker:[queue|topic:]destinationName</pre>
Modified: websites/production/camel/content/validate.html
==============================================================================
--- websites/production/camel/content/validate.html (original)
+++ websites/production/camel/content/validate.html Thu Nov 29 08:26:57 2018
@@ -155,9 +155,9 @@ from("file://inbox")
</pre>
</div></div>
-<h4 id="Validate-UsingThisPattern">Using This Pattern</h4>
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h4 id="Validate-UsingThisPattern">Using This Pattern</h4>
-<p>If you would like to use this EIP Pattern then please read the <a shape="rect" href="getting-started.html">Getting Started</a>, you may also find the <a shape="rect" href="architecture.html">Architecture</a> useful particularly the description of <a shape="rect" href="endpoint.html">Endpoint</a> and <a shape="rect" href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect" href="examples.html">Examples</a> first before trying this pattern out.</p></div>
+<p>If you would like to use this EIP Pattern then please read the <a shape="rect" href="getting-started.html">Getting Started</a>, you may also find the <a shape="rect" href="architecture.html">Architecture</a> useful particularly the description of <a shape="rect" href="endpoint.html">Endpoint</a> and <a shape="rect" href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect" href="examples.html">Examples</a> first before trying this pattern out.</p></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/vertx.html
==============================================================================
--- websites/production/camel/content/vertx.html (original)
+++ websites/production/camel/content/vertx.html Thu Nov 29 08:26:57 2018
@@ -104,8 +104,8 @@
VertxComponent vertxComponent = new VertxComponent();
vertxComponent.setVertx(vertx);
camelContext.addComponent("vertx", vertxComponent);</pre>
-</div></div><p></p><h3 id="Vertx-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+</div></div><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="Vertx-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/vm.html
==============================================================================
--- websites/production/camel/content/vm.html (original)
+++ websites/production/camel/content/vm.html Thu Nov 29 08:26:57 2018
@@ -148,8 +148,8 @@ from("vm:order.email").bean(MyOrderEmail
</pre>
</div></div>
-<h3 id="VM-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul>
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="VM-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
<ul class="alternate"><li><a shape="rect" href="seda.html">Seda</a></li></ul></div>
</td>
<td valign="top">
Modified: websites/production/camel/content/vtd-xml.html
==============================================================================
--- websites/production/camel/content/vtd-xml.html (original)
+++ websites/production/camel/content/vtd-xml.html Thu Nov 29 08:26:57 2018
@@ -123,8 +123,8 @@ This component is particular efficient f
<p>This will run the <a shape="rect" href="splitter.html">Splitter</a> in streaming mode using the <strong>vtdxml</strong> language.</p>
-<h3 id="VTD-XML-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="VTD-XML-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/what-are-the-dependencies.html
==============================================================================
--- websites/production/camel/content/what-are-the-dependencies.html (original)
+++ websites/production/camel/content/what-are-the-dependencies.html Thu Nov 29 08:26:57 2018
@@ -78,7 +78,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Whatarethedependencies-Whatarethedependencies?">What are the dependencies?</h2><p>Camel 2.6 or older can run on JDK 1.5 or better.<br clear="none"> Camel 2.7 onwards requires JDK 1.6 or JDK 1.7.<br clear="none">Camel 2.14 onwards requires JDK 1.7 or better.<br clear="none">Camel 2.18 onwards requires JDK 1.8.</p><h2 id="Whatarethedependencies-Whataretheruntimejardependencies?">What are the runtime jar dependencies?</h2><p>Apache Camel is designed to require a minimum number of dependencies for us so it is ideal for embedding into smart clients, message brokers, SOA frameworks and ESBs.</p><p></p><h2 id="Whatarethedependencies-CamelJARDependencies">Camel JAR Dependencies</h2><p>Camel core itself is lightweight and can run with a few .jars.</p><h4 id="Whatarethedependencies-camel-coredependenciesforCamel2.0orlower"><code>camel-core</code> dependencies for Camel 2.0 or lower</h4><ul class="alternate"><li><code>commons-logging-api.jar</code>
- API for commons logging</li><li>JAXB 2.1.x - XML stuff - Is provided in the JDK core from Java 1.6</li><li><code>activation.jar</code> - For Attachments support - Is provided in the JDK core from Java 1.6</li></ul><h4 id="Whatarethedependencies-camel-coredependenciesforCamel2.1-2.6"><code>camel-core</code> dependencies for Camel 2.1 - 2.6</h4><ul class="alternate"><li><code>commons-logging-api-1.1.jar</code> - API for commons logging</li><li><code>commons-management-1.0.jar</code> - API for JMX</li><li>JAXB 2.1.x - XML stuff - Is provided in the JDK core from Java 1.6</li><li><code>activation-1.1.jar</code> - For Attachments support - Is provided in the JDK core from Java 1.6</li></ul><h4 id="Whatarethedependencies-camel-coredependenciesforCamel2.7-2.8"><code>camel-core</code> dependencies for Camel 2.7 - 2.8</h4><ul class="alternate"><li><code>slf4j-api-1.5.11.jar</code> - API for slf4j logging</li><li><code>commons-management-1.0.jar</code> - API for JMX</li></ul><h4 id="W
hatarethedependencies-camel-coredependenciesforCamel2.9"><code>camel-core</code> dependencies for Camel 2.9</h4><ul class="alternate"><li><code>slf4j-api-1.6.1.jar</code> - API for slf4j logging</li></ul><h4 id="Whatarethedependencies-OptionalDependenciesforJMXforCamel1.x-2.8">Optional Dependencies for JMX for Camel 1.x - 2.8</h4><ul class="alternate"><li><code>spring-core.jar</code>, <code>spring-beans.jar</code>, <code>spring-context.jar</code>, <code>spring-aop.jar</code> - All 4 jars needed to use JMX with Camel (subject to change in the future).</li></ul><p>From <strong>Camel 2.9</strong>: the Spring JARs are no longer required for using JMX.</p><h2 id="Whatarethedependencies-OtherComponents">Other Components</h2><p>All the other <a shape="rect" href="components.html">Components</a> have a range of 3rd party .jars they depend on. They are listed in the maven pom files which files they require.</p><p>Other modules require other dependencies; such as camel-jms requires
a JMS provider. To see the exact dependencies of the other modules see the <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/maven/">Maven reports</a></p></div>
+<div class="wiki-content maincontent"><h2 id="Whatarethedependencies-Whatarethedependencies?">What are the dependencies?</h2><p>Camel 2.6 or older can run on JDK 1.5 or better.<br clear="none"> Camel 2.7 onwards requires JDK 1.6 or JDK 1.7.<br clear="none">Camel 2.14 onwards requires JDK 1.7 or better.<br clear="none">Camel 2.18 onwards requires JDK 1.8.</p><h2 id="Whatarethedependencies-Whataretheruntimejardependencies?">What are the runtime jar dependencies?</h2><p>Apache Camel is designed to require a minimum number of dependencies for us so it is ideal for embedding into smart clients, message brokers, SOA frameworks and ESBs.</p><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h2 id="Whatarethedependencies-CamelJARDependencies">Camel JAR Dependencies</h2><p>Camel core itself is lightweight and can run with a few .jars.</p><h4 id="Whatarethedependencies-camel-coredependenciesforCamel2.0orlower"><code>camel-core</code> dependencies for C
amel 2.0 or lower</h4><ul class="alternate"><li><code>commons-logging-api.jar</code> - API for commons logging</li><li>JAXB 2.1.x - XML stuff - Is provided in the JDK core from Java 1.6</li><li><code>activation.jar</code> - For Attachments support - Is provided in the JDK core from Java 1.6</li></ul><h4 id="Whatarethedependencies-camel-coredependenciesforCamel2.1-2.6"><code>camel-core</code> dependencies for Camel 2.1 - 2.6</h4><ul class="alternate"><li><code>commons-logging-api-1.1.jar</code> - API for commons logging</li><li><code>commons-management-1.0.jar</code> - API for JMX</li><li>JAXB 2.1.x - XML stuff - Is provided in the JDK core from Java 1.6</li><li><code>activation-1.1.jar</code> - For Attachments support - Is provided in the JDK core from Java 1.6</li></ul><h4 id="Whatarethedependencies-camel-coredependenciesforCamel2.7-2.8"><code>camel-core</code> dependencies for Camel 2.7 - 2.8</h4><ul class="alternate"><li><code>slf4j-api-1.5.11.jar</code> - API for slf4j logg
ing</li><li><code>commons-management-1.0.jar</code> - API for JMX</li></ul><h4 id="Whatarethedependencies-camel-coredependenciesforCamel2.9"><code>camel-core</code> dependencies for Camel 2.9</h4><ul class="alternate"><li><code>slf4j-api-1.6.1.jar</code> - API for slf4j logging</li></ul><h4 id="Whatarethedependencies-OptionalDependenciesforJMXforCamel1.x-2.8">Optional Dependencies for JMX for Camel 1.x - 2.8</h4><ul class="alternate"><li><code>spring-core.jar</code>, <code>spring-beans.jar</code>, <code>spring-context.jar</code>, <code>spring-aop.jar</code> - All 4 jars needed to use JMX with Camel (subject to change in the future).</li></ul><p>From <strong>Camel 2.9</strong>: the Spring JARs are no longer required for using JMX.</p><h2 id="Whatarethedependencies-OtherComponents">Other Components</h2><p>All the other <a shape="rect" href="components.html">Components</a> have a range of 3rd party .jars they depend on. They are listed in the maven pom files which files they
require.</p></div><p>Other modules require other dependencies; such as camel-jms requires a JMS provider. To see the exact dependencies of the other modules see the <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/maven/">Maven reports</a></p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/what-languages-are-supported.html
==============================================================================
--- websites/production/camel/content/what-languages-are-supported.html (original)
+++ websites/production/camel/content/what-languages-are-supported.html Thu Nov 29 08:26:57 2018
@@ -82,7 +82,7 @@
<p>Camel supports multiple <a shape="rect" href="languages.html">Languages</a> in the <a shape="rect" href="dsl.html">DSL</a> or <a shape="rect" href="xml-configuration.html">Xml Configuration</a> for maximum extensibility. The following is the list of currently supported languages</p>
-<ul><li><a shape="rect" href="bean-language.html">Bean Language</a> for using Java for expressions</li><li><a shape="rect" href="constant.html">Constant</a></li><li>the unified <a shape="rect" href="el.html">EL</a> from JSP and JSF</li><li><a shape="rect" href="header.html">Header</a></li><li><a shape="rect" href="jsonpath.html">JSonPath</a></li><li><a shape="rect" href="jxpath.html">JXPath</a></li><li><a shape="rect" href="mvel.html">Mvel</a></li><li><a shape="rect" href="ognl.html">OGNL</a></li><li><a shape="rect" href="ref-language.html">Ref Language</a></li><li><a shape="rect" href="exchangeproperty.html">ExchangeProperty</a> / <a shape="rect" href="property.html">Property</a></li><li><a shape="rect" href="scripting-languages.html">Scripting Languages</a> such as<ul><li><a shape="rect" href="beanshell.html">BeanShell</a></li><li><a shape="rect" href="javascript.html">JavaScript</a></li><li><a shape="rect" href="groovy.html">Groovy</a></li><li><a shape="rect" href="python.ht
ml">Python</a></li><li><a shape="rect" href="php.html">PHP</a></li><li><a shape="rect" href="ruby.html">Ruby</a></li></ul></li><li><a shape="rect" href="simple.html">Simple</a><ul><li><a shape="rect" href="file-language.html">File Language</a></li></ul></li><li><a shape="rect" href="spel.html">Spring Expression Language</a></li><li><a shape="rect" href="sql.html">SQL</a></li><li><a shape="rect" href="tokenizer.html">Tokenizer</a></li><li><a shape="rect" href="xpath.html">XPath</a></li><li><a shape="rect" href="xquery.html">XQuery</a></li><li><a shape="rect" href="vtd-xml.html">VTD-XML</a></li></ul><p>Most of these languages is also supported used as <a shape="rect" href="annotation-based-expression-language.html">Annotation Based Expression Language</a>.</p></div>
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><ul><li><a shape="rect" href="bean-language.html">Bean Language</a> for using Java for expressions</li><li><a shape="rect" href="constant.html">Constant</a></li><li>the unified <a shape="rect" href="el.html">EL</a> from JSP and JSF</li><li><a shape="rect" href="header.html">Header</a></li><li><a shape="rect" href="jsonpath.html">JSonPath</a></li><li><a shape="rect" href="jxpath.html">JXPath</a></li><li><a shape="rect" href="mvel.html">Mvel</a></li><li><a shape="rect" href="ognl.html">OGNL</a></li><li><a shape="rect" href="ref-language.html">Ref Language</a></li><li><a shape="rect" href="exchangeproperty.html">ExchangeProperty</a> / <a shape="rect" href="property.html">Property</a></li><li><a shape="rect" href="scripting-languages.html">Scripting Languages</a> such as<ul><li><a shape="rect" href="beanshell.html">BeanShell</a></li><li><a shape="rect" href="javascript.html">JavaScript</a></li><li><
a shape="rect" href="groovy.html">Groovy</a></li><li><a shape="rect" href="python.html">Python</a></li><li><a shape="rect" href="php.html">PHP</a></li><li><a shape="rect" href="ruby.html">Ruby</a></li></ul></li><li><a shape="rect" href="simple.html">Simple</a><ul><li><a shape="rect" href="file-language.html">File Language</a></li></ul></li><li><a shape="rect" href="spel.html">Spring Expression Language</a></li><li><a shape="rect" href="sql.html">SQL</a></li><li><a shape="rect" href="tokenizer.html">Tokenizer</a></li><li><a shape="rect" href="xpath.html">XPath</a></li><li><a shape="rect" href="xquery.html">XQuery</a></li><li><a shape="rect" href="vtd-xml.html">VTD-XML</a></li></ul><p>Most of these languages is also supported used as <a shape="rect" href="annotation-based-expression-language.html">Annotation Based Expression Language</a>.</p></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/why-cant-i-use-sign-in-my-password.html
==============================================================================
--- websites/production/camel/content/why-cant-i-use-sign-in-my-password.html (original)
+++ websites/production/camel/content/why-cant-i-use-sign-in-my-password.html Thu Nov 29 08:26:57 2018
@@ -78,7 +78,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Whycan'tIuse+signinmypassword-HowdoIconfigurepasswordoptionsonCamelendpointswithoutthevaluebeingencoded?">How do I configure password options on Camel endpoints without the value being encoded?</h2>
+<div class="wiki-content maincontent"><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h2 id="Whycan'tIuse+signinmypassword-HowdoIconfigurepasswordoptionsonCamelendpointswithoutthevaluebeingencoded?">How do I configure password options on Camel endpoints without the value being encoded?</h2>
<p>When you configure Camel endpoints using <a shape="rect" href="uris.html">URIs</a> then the parameter values gets url encoded by default.<br clear="none">
This can be a problem when you want to configure passwords <em>as is</em>.</p>
@@ -87,7 +87,7 @@ This can be a problem when you want to c
<h2 id="Whycan'tIuse+signinmypassword-SeeAlso">See Also</h2>
-<ul><li><a shape="rect" href="how-do-i-configure-endpoints.html">How Do I Configure Endpoints?</a></li></ul></div>
+<ul><li><a shape="rect" href="how-do-i-configure-endpoints.html">How Do I Configure Endpoints?</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/xml-reference.html
==============================================================================
--- websites/production/camel/content/xml-reference.html (original)
+++ websites/production/camel/content/xml-reference.html Thu Nov 29 08:26:57 2018
@@ -87,7 +87,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
[... 6 lines stripped ...]
Modified: websites/production/camel/content/xmpp.html
==============================================================================
--- websites/production/camel/content/xmpp.html (original)
+++ websites/production/camel/content/xmpp.html Thu Nov 29 08:26:57 2018
@@ -127,8 +127,8 @@ to("activemq:krypton.talk");
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("direct:start").
to("xmpp://talk.google.com:5222/touser@gmail.com?serviceName=gmail.com&user=fromuser&password=secret").
to("mock:result");</pre>
-</div></div><p> </p><p></p><h3 id="XMPP-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+</div></div><p> </p><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="XMPP-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/xquery-endpoint.html
==============================================================================
--- websites/production/camel/content/xquery-endpoint.html (original)
+++ websites/production/camel/content/xquery-endpoint.html Thu Nov 29 08:26:57 2018
@@ -135,8 +135,8 @@ from("activemq:My.Queue").
</pre>
</div></div>
-<h3 id="XQueryEndpoint-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="XQueryEndpoint-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/xslt.html
==============================================================================
--- websites/production/camel/content/xslt.html (original)
+++ websites/production/camel/content/xslt.html Thu Nov 29 08:26:57 2018
@@ -202,8 +202,8 @@ context.addRoutes(new RouteBuilder() {
</body>
</html>
</xsl:template></pre>
-</div></div><p>This information is not available on the Exchange stored as an Exception that contains the message in the <code>getMessage()</code> method on the exception. The exception is stored on the Exchange as a warning with the key<span style="line-height: 1.4285715;"> </span><code style="line-height: 1.4285715;">Exchange.XSLT_WARNING.</code></p><h3 id="XSLT-NotesonusingXSLTandJavaVersions">Notes on using XSLT and Java Versions</h3><p>Here are some observations from Sameer, a Camel user, which he kindly shared with us:</p><blockquote><p>In case anybody faces issues with the XSLT endpoint please review these points.</p><p>I was trying to use an xslt endpoint for a simple transformation from one xml to another using a simple xsl. The output xml kept appearing (after the xslt processor in the route) with outermost xml tag with no content within.</p><p>No explanations show up in the DEBUG logs. On the TRACE logs however I did find some error/warning indicating that the XMLCon
verter bean could no be initialized.</p><p>After a few hours of cranking my mind, I had to do the following to get it to work (thanks to some posts on the users forum that gave some clue):</p><p>1. Use the transformerFactory option in the route <code>("xslt:my-transformer.xsl?transformerFactory=tFactory")</code> with the <code>tFactory</code> bean having bean defined in the spring context for <code>class="org.apache.xalan.xsltc.trax.TransformerFactoryImpl"</code>.<br clear="none"> 2. Added the Xalan jar into my maven pom.</p><p>My guess is that the default xml parsing mechanism supplied within the JDK (I am using 1.6.0_03) does not work right in this context and does not throw up any error either. When I switched to Xalan this way it works. This is not a Camel issue, but might need a mention on the xslt component page.</p><p>Another note, jdk 1.6.0_03 ships with JAXB 2.0 while Camel needs 2.1. One workaround is to add the 2.1 jar to the <code>jre/lib/endorsed</code> directory for th
e jvm or as specified by the container.</p><p>Hope this post saves newbie Camel riders some time.</p></blockquote><p></p><h3 id="XSLT-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+</div></div><p>This information is not available on the Exchange stored as an Exception that contains the message in the <code>getMessage()</code> method on the exception. The exception is stored on the Exchange as a warning with the key<span style="line-height: 1.4285715;"> </span><code style="line-height: 1.4285715;">Exchange.XSLT_WARNING.</code></p><h3 id="XSLT-NotesonusingXSLTandJavaVersions">Notes on using XSLT and Java Versions</h3><p>Here are some observations from Sameer, a Camel user, which he kindly shared with us:</p><blockquote><p>In case anybody faces issues with the XSLT endpoint please review these points.</p><p>I was trying to use an xslt endpoint for a simple transformation from one xml to another using a simple xsl. The output xml kept appearing (after the xslt processor in the route) with outermost xml tag with no content within.</p><p>No explanations show up in the DEBUG logs. On the TRACE logs however I did find some error/warning indicating that the XMLCon
verter bean could no be initialized.</p><p>After a few hours of cranking my mind, I had to do the following to get it to work (thanks to some posts on the users forum that gave some clue):</p><p>1. Use the transformerFactory option in the route <code>("xslt:my-transformer.xsl?transformerFactory=tFactory")</code> with the <code>tFactory</code> bean having bean defined in the spring context for <code>class="org.apache.xalan.xsltc.trax.TransformerFactoryImpl"</code>.<br clear="none"> 2. Added the Xalan jar into my maven pom.</p><p>My guess is that the default xml parsing mechanism supplied within the JDK (I am using 1.6.0_03) does not work right in this context and does not throw up any error either. When I switched to Xalan this way it works. This is not a Camel issue, but might need a mention on the xslt component page.</p><p>Another note, jdk 1.6.0_03 ships with JAXB 2.0 while Camel needs 2.1. One workaround is to add the 2.1 jar to the <code>jre/lib/endorsed</code> directory for th
e jvm or as specified by the container.</p><p>Hope this post saves newbie Camel riders some time.</p></blockquote><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="XSLT-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/yammer.html
==============================================================================
--- websites/production/camel/content/yammer.html (original)
+++ websites/production/camel/content/yammer.html Thu Nov 29 08:26:57 2018
@@ -242,8 +242,8 @@
<h3 id="Yammer-Usinganenricher">Using an enricher</h3><p>It is helpful sometimes (or maybe always in the case of users or relationship consumers) to use an enricher pattern rather than a route initiated with one of the polling consumers in camel-yammer. This is because the consumers will fire repeatedly, however often you set the delay for. If you just want to look up a user's data, or grab a message at a point in time, it is better to call that consumer once and then get one with your route.</p><p>Lets say you have a route that at some point needs to go out and fetch user data for the current user. Rather than polling for this user over and over again, use the pollEnrich DSL method:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("direct:start").pollEnrich("yammer:current?consumerKey=aConsumerKey&consumerSecret=aConsumerSecretKey&accessToken=aAccessToken").to("mock:result");
</pre>
-</div></div><p>This will go out and fetch the current user's User object and set it as the Camel message body.</p><p></p><h3 id="Yammer-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+</div></div><p>This will go out and fetch the current user's User object and set it as the Camel message body.</p><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="Yammer-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/zookeeper.html
==============================================================================
--- websites/production/camel/content/zookeeper.html (original)
+++ websites/production/camel/content/zookeeper.html Thu Nov 29 08:26:57 2018
@@ -141,8 +141,8 @@ template.sendBodyAndHeader("direct:creat
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">ZooKeeperRoutePolicy policy = new ZooKeeperRoutePolicy("zookeeper:localhost:39913/someapp/somepolicy", 1);
from("direct:policy-controlled").routePolicy(policy).to("mock:controlled");
</pre>
-</div></div><p></p><h3 id="Zookeeper-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
+</div></div><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="Zookeeper-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div></div>
</td>
<td valign="top">
<div class="navigation">