Modified: websites/production/camel/content/mvel-component.html
==============================================================================
--- websites/production/camel/content/mvel-component.html (original)
+++ websites/production/camel/content/mvel-component.html Thu Sep 14 19:25:46
2017
@@ -92,7 +92,7 @@
<p>Maven users will need to add the following dependency to their
<code>pom.xml</code> for this component:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-mvel</artifactId>
Modified: websites/production/camel/content/mybatis-example.html
==============================================================================
--- websites/production/camel/content/mybatis-example.html (original)
+++ websites/production/camel/content/mybatis-example.html Thu Sep 14 19:25:46
2017
@@ -89,16 +89,16 @@
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[mvn install
]]></script>
</div></div><h3 id="MyBatisExample-About">About</h3><p>This example shows how
to exchange data using a shared database table.</p><p>The example has two Camel
routes. The first route insert new data into the table, triggered by a timer to
run every 5th second.<br clear="none"> The second route pickup the newly
inserted rows from the table, process the row(s), and mark the row(s) as
processed when done; to avoid picking up the same rows again.</p><h3
id="MyBatisExample-Implementation">Implementation</h3><p>In the
<code>camel-mybatis.xml</code> file in the
<code>src/main/resources/OSGI-INF/blueprint</code> folder we have the Blueprint
XML file. This example uses an embedded Database so we use the following bean
to create and drop the table(s).</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <bean id="initDatabase"
class="org.apache.camel.example.mybatis.DatabaseBean"
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <bean id="initDatabase"
class="org.apache.camel.example.mybatis.DatabaseBean"
init-method="create" destroy-method="destroy">
<property name="camelContext"
ref="myBatisAndCamel"/>
</bean>
]]></script>
</div></div><p>This example uses a bean to generate orders</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <bean id="orderService"
class="org.apache.camel.example.mybatis.OrderService"/>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <bean id="orderService"
class="org.apache.camel.example.mybatis.OrderService"/>
]]></script>
</div></div><p>And the <a shape="rect"
href="camelcontext.html">CamelContext</a> has two routes as shown
below:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <camelContext
id="myBatisAndCamel"
xmlns="http://camel.apache.org/schema/blueprint">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <camelContext
id="myBatisAndCamel"
xmlns="http://camel.apache.org/schema/blueprint">
<!-- route that generate new orders and insert them in the database
-->
<route id="generateOrder-route">
@@ -121,7 +121,7 @@
</camelContext>
]]></script>
</div></div><h4 id="MyBatisExample-MyBatisSqlMapConfig.xml">MyBatis
SqlMapConfig.xml</h4><p><a shape="rect" href="mybatis.html">MyBatis</a> is
configured using a <code>SqlMapConfig.xml</code> file located in the root of
the classpath, eg in <code>src/main/resources</code>.<br clear="none"> This
configuration files setup <a shape="rect" href="mybatis.html">MyBatis</a> as
well a pooled data source</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width:
1px;"><b>MyBatis SqlMapConfig.xml</b></div><div class="codeContent panelContent
pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<!DOCTYPE configuration
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<!DOCTYPE configuration
PUBLIC "-//mybatis.org//DTD Config 3.0//EN"
"http://mybatis.org/dtd/mybatis-3-config.dtd">
@@ -205,7 +205,7 @@
}
]]></script>
</div></div><p>And the <a shape="rect" href="mybatis.html">MyBatis</a> mapping
file <code>Order.xml</code> is located in
<code>src/main/resources/org/apache/camel/example/mybatis</code> where we map
from SQL to this Order POJO, as shown below:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeHeader panelHeader pdl"
style="border-bottom-width: 1px;"><b>MyBatis mapping file for
Order</b></div><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<!DOCTYPE mapper
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<!DOCTYPE mapper
PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN"
"http://mybatis.org/dtd/mybatis-3-mapper.dtd">
Modified: websites/production/camel/content/nats.html
==============================================================================
--- websites/production/camel/content/nats.html (original)
+++ websites/production/camel/content/nats.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2 id="NATS-NATSComponent">NATS
Component</h2><div class="confluence-information-macro
confluence-information-macro-tip"><p class="title">Available since Camel
2.17.0</p><span class="aui-icon aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"> </div></div><p><a shape="rect"
class="external-link" href="http://nats.io/";
rel="nofollow">NATS</a> <span>is a fast and reliable messaging
platform.</span></p><p>Maven users will need to add the following dependency to
their <code>pom.xml</code> for this component.</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-nats</artifactId>
<!-- use the same version as your Camel core version -->
Modified: websites/production/camel/content/netty-http-server-example.html
==============================================================================
--- websites/production/camel/content/netty-http-server-example.html (original)
+++ websites/production/camel/content/netty-http-server-example.html Thu Sep 14
19:25:46 2017
@@ -115,7 +115,7 @@ mvn package
<p>And finally we need to enlist the shared <a shape="rect"
href="netty-http.html">Netty HTTP</a> server in the OSGi Service Registry, so
we can refer and use it from other bundles.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
@@ -151,7 +151,7 @@ mvn package
<p>In the Camel route, we then use the <code>nettySharedHttpServer</code>
option to use the shared server, with
<code>nettySharedHttpServer=#sharedNettyHttpServer</code>.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
Modified: websites/production/camel/content/netty-http.html
==============================================================================
--- websites/production/camel/content/netty-http.html (original)
+++ websites/production/camel/content/netty-http.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2
id="NettyHTTP-NettyHTTPComponent">Netty HTTP Component</h2><p><strong>Available
as of Camel 2.12</strong></p><p>The <strong>netty-http</strong> component is an
extension to <a shape="rect" href="netty.html">Netty</a> component to
facilitiate HTTP transport with <a shape="rect"
href="netty.html">Netty</a>.</p><p>This camel component supports both producer
and consumer endpoints.</p><div class="confluence-information-macro
confluence-information-macro-warning"><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>This component is deprecated. You
should use <a shape="rect" href="netty4-http.html">Netty4
HTTP</a>.</p></div></div><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Stream</p><span
class="aui-icon aui-icon-small aui-iconfont-info
confluence-information-macro-icon"></span><div class="confluen
ce-information-macro-body"><p>Netty is stream based, which means the input it
receives is submitted to Camel as a stream. That means you will only be able to
read the content of the stream <strong>once</strong>.<br clear="none"> If you
find a situation where the message body appears to be empty or you need to
access the data multiple times (eg: doing multicasting, or redelivery error
handling)<br clear="none"> you should use <a shape="rect"
href="stream-caching.html">Stream caching</a> or convert the message body to a
<code>String</code> which is safe to be re-read multiple
times.</p><p><span>Notice Netty4 HTTP reads the entire stream into memory using
</span><code>io.netty.handler.codec.http.HttpObjectAggregator</code><span> to
build the entire full http message. But the resulting message is still a stream
based message which is readable once.</span></p></div></div><p>Maven users will
need to add the following dependency to their <code>pom.xml</code> for this
component:</p><div cla
ss="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-netty-http</artifactId>
<version>x.x.x</version>
@@ -152,14 +152,14 @@ from("netty-http:http://0.0.0.0:{{p
.transform().constant("Bye Camel");
]]></script>
</div></div><h4
id="NettyHTTP-Reusingsameserverbootstrapconfigurationwithmultipleroutes">Reusing
same server bootstrap configuration with multiple routes</h4><p>By configuring
the common server bootstrap option in an single instance of a
<code>org.apache.camel.component.netty.NettyServerBootstrapConfiguration</code>
type, we can use the <code>bootstrapConfiguration</code> option on the <a
shape="rect" href="netty-http.html">Netty HTTP</a> consumers to refer and reuse
the same options across all consumers.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean
id="nettyHttpBootstrapOptions"
class="org.apache.camel.component.netty.NettyServerBootstrapConfiguration">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean
id="nettyHttpBootstrapOptions"
class="org.apache.camel.component.netty.NettyServerBootstrapConfiguration">
<property name="backlog" value="200"/>
<property name="connectTimeout" value="20000"/>
<property name="workerCount" value="16"/>
</bean>
]]></script>
</div></div><p>And in the routes you refer to this option as shown
below</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<route>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<route>
<from
uri="netty-http:http://0.0.0.0:{{port}}/foo?bootstrapConfiguration=#nettyHttpBootstrapOptions"/>
...
</route>
@@ -181,7 +181,7 @@ from("netty-http:http://0.0.0.0:{{p
</route>
]]></script>
</div></div><p>The realm name is mandatory to enable basic authentication. By
default the JAAS based authenticator is used, which will use the realm name
specified (karaf in the example above) and use the JAAS realm and the JAAS
{{LoginModule}}s of this realm for authentication.</p><p>End user of Apache
Karaf / ServiceMix has a karaf realm out of the box, and hence why the example
above would work out of the box in these containers.</p><h4
id="NettyHTTP-SpecifyingACLonwebresources">Specifying ACL on web
resources</h4><p>The
<code>org.apache.camel.component.netty.http.SecurityConstraint</code> allows to
define constrains on web resources. And the
<code>org.apache.camel.component.netty.http.SecurityConstraintMapping</code> is
provided out of the box, allowing to easily define inclusions and exclusions
with roles.</p><p>For example as shown below in the XML DSL, we define the
constraint bean:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent
pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <bean id="constraint"
class="org.apache.camel.component.netty.http.SecurityConstraintMapping">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <bean id="constraint"
class="org.apache.camel.component.netty.http.SecurityConstraintMapping">
<!-- inclusions defines url -> roles restrictions -->
<!-- a * should be used for any role accepted (or even no roles) -->
<property name="inclusions">
@@ -200,7 +200,7 @@ from("netty-http:http://0.0.0.0:{{p
</bean>
]]></script>
</div></div><p>The constraint above is define so that</p><ul
class="alternate"><li>access to /* is restricted and any roles is accepted
(also if user has no roles)</li><li>access to /admin/* requires the admin
role</li><li>access to /guest/* requires the admin or guest role</li><li>access
to /public/* is an exclusion which means no authentication is needed, and is
therefore public for everyone without logging in</li></ul><p>To use this
constraint we just need to refer to the bean id as shown below:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<route>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<route>
<from
uri="netty-http:http://0.0.0.0:{{port}}/foo?matchOnUriPrefix=true&amp;securityConfiguration.realm=karaf&amp;securityConfiguration.securityConstraint=#constraint"/>
...
</route>
Modified: websites/production/camel/content/netty4-http.html
==============================================================================
--- websites/production/camel/content/netty4-http.html (original)
+++ websites/production/camel/content/netty4-http.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2
id="Netty4HTTP-Netty4HTTPComponent">Netty4 HTTP
Component</h2><p><strong>Available as of Camel 2.14</strong></p><p
class="confluence-link">The <strong>netty4-http</strong> component is an
extension to <a shape="rect" href="netty4.html">Netty4</a> component to
facilitiate HTTP transport with <a shape="rect"
href="netty4.html">Netty4</a>.</p><p>This camel component supports both
producer and consumer endpoints.</p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Stream</p><span
class="aui-icon aui-icon-small aui-iconfont-info
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>Netty is stream based, which means
the input it receives is submitted to Camel as a stream. That means you will
only be able to read the content of the stream <strong>once</strong>.<br
clear="none"> If you find a situation where the message body appears to be
empty or you need
to access the data multiple times (eg: doing multicasting, or redelivery
error handling)<br clear="none"> you should use <a shape="rect"
href="stream-caching.html">Stream caching</a> or convert the message body to a
<code>String</code> which is safe to be re-read multiple times.</p><p>Notice
Netty4 HTTP reads the entire stream into memory using
<code>io.netty.handler.codec.http.HttpObjectAggregator</code> to build the
entire full http message. But the resulting message is still a stream based
message which is readable once.</p></div></div><p>Maven users will need to add
the following dependency to their <code>pom.xml</code> for this
component:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-netty4-http</artifactId>
<version>x.x.x</version>
@@ -152,14 +152,14 @@ from("netty4-http:http://0.0.0.0:{{
.transform().constant("Bye Camel");
]]></script>
</div></div><h4
id="Netty4HTTP-Reusingsameserverbootstrapconfigurationwithmultipleroutes">Reusing
same server bootstrap configuration with multiple routes</h4><p>By configuring
the common server bootstrap option in an single instance of a
<code>org.apache.camel.component.netty4.NettyServerBootstrapConfiguration</code>
type, we can use the <code>bootstrapConfiguration</code> option on the Netty4
HTTP consumers to refer and reuse the same options across all
consumers.</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean
id="nettyHttpBootstrapOptions"
class="org.apache.camel.component.netty4.NettyServerBootstrapConfiguration">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean
id="nettyHttpBootstrapOptions"
class="org.apache.camel.component.netty4.NettyServerBootstrapConfiguration">
<property name="backlog" value="200"/>
<property name="connectionTimeout" value="20000"/>
<property name="workerCount" value="16"/>
</bean>
]]></script>
</div></div><p>And in the routes you refer to this option as shown
below</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<route>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<route>
<from
uri="netty4-http:http://0.0.0.0:{{port}}/foo?bootstrapConfiguration=#nettyHttpBootstrapOptions"/>
...
</route>
@@ -181,7 +181,7 @@ from("netty4-http:http://0.0.0.0:{{
</route>
]]></script>
</div></div><p>The realm name is mandatory to enable basic authentication. By
default the JAAS based authenticator is used, which will use the realm name
specified (karaf in the example above) and use the JAAS realm and the JAAS
{{LoginModule}}s of this realm for authentication.</p><p>End user of Apache
Karaf / ServiceMix has a karaf realm out of the box, and hence why the example
above would work out of the box in these containers.</p><h4
id="Netty4HTTP-SpecifyingACLonwebresources">Specifying ACL on web
resources</h4><p>The
<code>org.apache.camel.component.netty4.http.SecurityConstraint</code> allows
to define constrains on web resources. And the
<code>org.apache.camel.component.netty.http.SecurityConstraintMapping</code> is
provided out of the box, allowing to easily define inclusions and exclusions
with roles.</p><p>For example as shown below in the XML DSL, we define the
constraint bean:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelConte
nt pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <bean id="constraint"
class="org.apache.camel.component.netty4.http.SecurityConstraintMapping">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <bean id="constraint"
class="org.apache.camel.component.netty4.http.SecurityConstraintMapping">
<!-- inclusions defines url -> roles restrictions -->
<!-- a * should be used for any role accepted (or even no roles) -->
<property name="inclusions">
@@ -200,7 +200,7 @@ from("netty4-http:http://0.0.0.0:{{
</bean>
]]></script>
</div></div><p>The constraint above is define so that</p><ul
class="alternate"><li>access to /* is restricted and any roles is accepted
(also if user has no roles)</li><li>access to /admin/* requires the admin
role</li><li>access to /guest/* requires the admin or guest role</li><li>access
to /public/* is an exclusion which means no authentication is needed, and is
therefore public for everyone without logging in</li></ul><p>To use this
constraint we just need to refer to the bean id as shown below:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<route>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<route>
<from
uri="netty4-http:http://0.0.0.0:{{port}}/foo?matchOnUriPrefix=true&amp;securityConfiguration.realm=karaf&amp;securityConfiguration.securityConstraint=#constraint"/>
...
</route>
Modified: websites/production/camel/content/netty4.html
==============================================================================
--- websites/production/camel/content/netty4.html (original)
+++ websites/production/camel/content/netty4.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2 id="Netty4-NettyComponent">Netty
Component</h2><p><strong>Available as of Camel 2.14</strong></p><p>The
<strong>netty4</strong> component in Camel is a socket communication component,
based on the <a shape="rect" class="external-link" href="http://netty.io/";
rel="nofollow">Netty</a> project version 4.<br clear="none"> Netty is a NIO
client server framework which enables quick and easy development of network
applications such as protocol servers and clients.<br clear="none"> Netty
greatly simplifies and streamlines network programming such as TCP and UDP
socket server.</p><p>This camel component supports both producer and consumer
endpoints.</p><p>The Netty component has several options and allows
fine-grained control of a number of TCP/UDP communication parameters (buffer
sizes, keepAlives, tcpNoDelay etc) and facilitates both In-Only and In-Out
communication on a Camel route.</p><p>Maven users will need to add the
following dependency to th
eir <code>pom.xml</code> for this component:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-netty4</artifactId>
<version>x.x.x</version>
@@ -141,7 +141,7 @@ NettyComponent nettyComponent = getConte
nettyComponent.setSslContextParameters(scp);
]]></script>
</div></div><h6 id="Netty4-SpringDSLbasedconfigurationofendpoint">Spring DSL
based configuration of endpoint</h6><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[...
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[...
<camel:sslContextParameters
id="sslContextParameters">
<camel:keyManagers
@@ -312,7 +312,7 @@ context.addRoutes(new RouteBuilder() {
]]></script>
</div></div><h3 id="Netty4-ReusingNettybossandworkerthreadpools">Reusing Netty
boss and worker thread pools</h3><p><strong>Available as of Camel
2.12</strong></p><p>Netty has two kind of thread pools: boss and worker. By
default each Netty consumer and producer has their private thread pools. If you
want to reuse these thread pools among multiple consumers or producers then the
thread pools must be created and enlisted in the <a shape="rect"
href="registry.html">Registry</a>.</p><p>For example using Spring XML we can
create a shared worker thread pool using the
<code>NettyWorkerPoolBuilder</code> with 2 worker threads as shown
below:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <!-- use the worker pool builder to
create to help create the shared thread pool -->
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <!-- use the worker pool builder to
create to help create the shared thread pool -->
<bean id="poolBuilder"
class="org.apache.camel.component.netty.NettyWorkerPoolBuilder">
<property name="workerCount" value="2"/>
</bean>
@@ -323,14 +323,14 @@ context.addRoutes(new RouteBuilder() {
</bean>
]]></script>
</div></div><div class="confluence-information-macro
confluence-information-macro-tip"><span class="aui-icon aui-icon-small
aui-iconfont-approve confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>For boss thread pool there is a
<code>org.apache.camel.component.netty4.NettyServerBossPoolBuilder</code>
builder for Netty consumers, and a
<code>org.apache.camel.component.netty4.NettyClientBossPoolBuilder</code> for
the Netty produces.</p></div></div><p>Then in the Camel routes we can refer to
this worker pools by configuring the <code>workerPool</code> option in the <a
shape="rect" class="unresolved" href="#">URI</a> as shown below:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <route>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <route>
<from
uri="netty4:tcp://localhost:5021?textline=true&amp;sync=true&amp;workerPool=#sharedPool&amp;usingExecutorService=false"/>
<to uri="log:result"/>
...
</route>
]]></script>
</div></div><p>And if we have another route we can refer to the shared worker
pool:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <route>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <route>
<from
uri="netty4:tcp://localhost:5022?textline=true&amp;sync=true&amp;workerPool=#sharedPool&amp;usingExecutorService=false"/>
<to uri="log:result"/>
...
Modified: websites/production/camel/content/news.html
==============================================================================
--- websites/production/camel/content/news.html (original)
+++ websites/production/camel/content/news.html Thu Sep 14 19:25:46 2017
@@ -88,6 +88,26 @@
<img class="userLogo logo"
src="news.userimage/gzurowski-89607-pp-wojtek-avatar.png" alt="User icon:
gzurowski" title="gzurowski">
</a> </span>
<span class="blogHeading">
+ <a shape="rect" class="blogHeading"
href="2017/09/14/apache-camel-2193-released.html">Apache Camel 2.19.3
Released</a>
+ </span><div class="page-metadata not-personal"> <a
shape="rect" class="url fn confluence-userlink" href="
/confluence/display/~gzurowski ">Gregor Zurowski</a> posted on Sep 14,
2017</div>
+
+ </div>
+
+ <div class="wiki-content">
+ <p>The Camel community announces the immediate availability of the new
patch release Camel 2.19.3. This release contains 40 fixes applied in the past
few weeks by the community on the Camel 2.19.x maintenance branch.</p><p>The
artifacts are published and ready for you to <a shape="rect"
class="external-link"
href="http://camel.apache.org/download.html";>download</a> either from the
Apache mirrors or from the Central Maven repository. For more details please
take a look at the <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341135&projectId=12311211";>release
notes</a>.</p><p>Many thanks to all who made this release possible.</p><p>On
behalf of the Camel PMC,<br clear="none">Gregor Zurowski</p>
+ </div>
+
+
+ </div>
+
+
+<div class="blog-post-listing">
+ <div class="logo-heading-block">
+ <span class="logoBlock">
+ <a shape="rect" class="userLogoLink" href="
/confluence/display/~gzurowski ">
+ <img class="userLogo logo"
src="news.userimage/gzurowski-89607-pp-wojtek-avatar.png" alt="User icon:
gzurowski" title="gzurowski">
+ </a> </span>
+ <span class="blogHeading">
<a shape="rect" class="blogHeading"
href="2017/08/01/apache-camel-2192-released.html">Apache Camel 2.19.2
Released</a>
</span><div class="page-metadata not-personal"> <a
shape="rect" class="url fn confluence-userlink" href="
/confluence/display/~gzurowski ">Gregor Zurowski</a> posted on Aug 01,
2017</div>
@@ -458,26 +478,6 @@
</div>
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="
/confluence/display/~gzurowski ">
- <img class="userLogo logo"
src="news.userimage/gzurowski-89607-pp-wojtek-avatar.png" alt="User icon:
gzurowski" title="gzurowski">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading"
href="2016/11/30/apache-camel-2174-released.html">Apache Camel 2.17.4
Released</a>
- </span><div class="page-metadata not-personal"> <a
shape="rect" class="url fn confluence-userlink" href="
/confluence/display/~gzurowski ">Gregor Zurowski</a> posted on Nov 30,
2016</div>
-
- </div>
-
- <div class="wiki-content">
- <p>The Camel community announces the immediate availability of the new
patch release Camel 2.17.4. This release contains 40+ fixes applied in the past
few weeks by the community on the Camel 2.17.x maintenance branch.</p><p>The
artifacts are published and ready for you to <a shape="rect"
class="external-link"
href="http://camel.apache.org/download.html";>download</a> either from the
Apache mirrors or from the Central Maven repository. For more details please
take a look at the <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338067&projectId=12311211";>release
notes</a>.</p><p>Many thanks to all who made this release possible.</p><p>On
behalf of the Camel PMC,<br clear="none">Gregor Zurowski</p>
- </div>
-
-
</div>
</div>
</td>
Modified: websites/production/camel/content/nmr.html
==============================================================================
--- websites/production/camel/content/nmr.html (original)
+++ websites/production/camel/content/nmr.html Thu Sep 14 19:25:46 2017
@@ -119,7 +119,7 @@ install -s mvn:org.apache.servicemix.cam
<p>You also need to instantiate the NMR component. You can do this by editing
your Spring configuration file, <code>META-INF/spring/*.xml</code>, and adding
the following <code>bean</code> instance:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<beans xmlns:osgi="http://www.springframework.org/schema/osgi"
... >
...
<bean id="nmr"
class="org.apache.servicemix.camel.nmr.ServiceMixComponent">
Modified: websites/production/camel/content/openshift.html
==============================================================================
--- websites/production/camel/content/openshift.html (original)
+++ websites/production/camel/content/openshift.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2
id="Openshift-OpenshiftComponent">Openshift Component</h2><p><strong>Available
as of Camel 2.14</strong></p><p>The <strong>openshift</strong> component is a
component for managing your <a shape="rect" class="external-link"
href="https://www.openshift.com/"; rel="nofollow">OpenShift</a>
applications. </p><p><span style="line-height: 1.4285715;">Maven users
will need to add the following dependency to their </span><code
style="line-height: 1.4285715;">pom.xml</code><span style="line-height:
1.4285715;"> for this component:</span></p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-openshift</artifactId>
<version>x.x.x</version>
Modified: websites/production/camel/content/optaplanner.html
==============================================================================
--- websites/production/camel/content/optaplanner.html (original)
+++ websites/production/camel/content/optaplanner.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2
id="OptaPlanner-OptaPlanner">OptaPlanner</h2><p><strong>Available as of Camel
2.13</strong></p><p>The <strong>optaplanner:</strong> component solves the
planning problem contained in a message with <a shape="rect"
class="external-link" href="http://www.optaplanner.org/";
rel="nofollow">OptaPlanner</a>.<br clear="none"> For example: feed it an
unsolved Vehicle Routing problem and it solves it.</p><p>The component supports
consumer as BestSolutionChangedEvent listener and producer for processing
Solution and ProblemFactChange</p><p>Maven users will need to add the following
dependency to their <code>pom.xml</code> for this component:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-optaplanner</artifactId>
<version>x.x.x</version><!-- use the same version as your
Camel core version -->
@@ -96,7 +96,7 @@
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[optaplanner:solverConfig[?options]
]]></script>
</div></div><p>The <strong>solverConfig</strong> is the classpath-local URI of
the solverConfig, for example
<code>/org/foo/barSolverConfig.xml</code>.</p><p>You can append query options
to the URI in the following format,
<code>?option=value&option=value&...</code></p><h3
id="OptaPlanner-URIOptions(sincev2.16)">URI Options<strong> (since v
2.16)</strong></h3><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Context</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>solverId</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>DEFAULT_SOLVER</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>String</p></
td><td colspan="1" rowspan="1" class="confluenceTd"><p>Shared</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The endpoint keeps a map of
Solver instances. solverId specifies a the map key to use.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>threadPoolSize</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>10</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>int</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Producer</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Specifies the size the of thread pool to use for
processing async Solution messages.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>async</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Boolean</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Producer</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Specify whether to use an
other thread for submitting Solution instances rather than blocking the
current thread.</p></td></tr></tbody></table></div><h3
id="OptaPlanner-MessageHeaders(sincev2.16)">Message Headers<strong> (since v
2.16)</strong></h3><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Context</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd">CamelOptaPlannerSolverId</td><td colspan="1"
rowspan="1" class="confluenceTd">null</td><td colspan="1" rowspan="1"
class="confluenceTd">String</td><td colspan="1" rowspan="1"
class="confluenceTd">Shared</td><td colspan="1" rowspan="1"
class="confluenceTd">Specifies the solverId to use</td></tr><tr><td col
span="1" rowspan="1" class="confluenceTd">CamelOptaPlannerIsAsync</td><td
colspan="1" rowspan="1" class="confluenceTd">PUT</td><td colspan="1"
rowspan="1" class="confluenceTd">String</td><td colspan="1" rowspan="1"
class="confluenceTd">Producer</td><td colspan="1" rowspan="1"
class="confluenceTd">Specify whether to use another thread for submitting
Solution instances rather than blocking the current
thread.</td></tr></tbody></table></div><h3 id="OptaPlanner-MessageBody">Message
Body</h3><p>Camel takes the planning problem for the IN body, solves it and
returns it on the OUT body.<br clear="none"> (since v 2.16) The IN body object
supports the following use cases:</p><ul><li>If the body is instance of
Solution, then it will be solved using the solver identified by solverId and
either synchronously or asynchronously.</li><li>If the body is instance of
ProblemFactChange, then it will trigger <span style="color:
rgb(49,55,57);">addProblemFactChange</span>. If the processing is asynchron
ously, then it will wait till isEveryProblemFactChangeProcessed before
returning result.</li><li>If the body is none of the above types, then the
producer will return the best result from the solver identified by
solverId</li></ul><h3 id="OptaPlanner-Termination">Termination</h3><p>The
solving will take as long as specified in the
<code>solverConfig</code>.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<solver>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<solver>
...
<termination>
<!-- Terminate after 10 seconds, unless it's not feasible by then
yet -->
Modified: websites/production/camel/content/paho.html
==============================================================================
--- websites/production/camel/content/paho.html (original)
+++ websites/production/camel/content/paho.html Thu Sep 14 19:25:46 2017
@@ -98,7 +98,7 @@
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("paho:some/queue?brokerUrl=tcp://iot.eclipse.org:1883").
to("mock:test");]]></script>
</div></div><p> </p></div><h3
id="Paho-Addingthecomponenttotheproject">Adding the component to the
project</h3><p>Maven users will need to add the following dependency to their
<code>pom.xml</code> for this component:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-paho</artifactId>
<version>x.y.z</version>
@@ -106,7 +106,7 @@
</dependency>
]]></script>
</div></div><p>Keep in mind that Paho artifacts are not hosted in the Maven
Central, so you need to add Eclipse Paho repository to your POM xml
file:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<repositories>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<repositories>
<repository>
<id>eclipse-paho</id>
<url>https://repo.eclipse.org/content/repositories/paho-releases</url>
Modified: websites/production/camel/content/parameter-binding-annotations.html
==============================================================================
--- websites/production/camel/content/parameter-binding-annotations.html
(original)
+++ websites/production/camel/content/parameter-binding-annotations.html Thu
Sep 14 19:25:46 2017
@@ -238,7 +238,7 @@ public class MySimpleIdGenerator {
<p>And finally we just need to remember to have our bean registered in the
Spring <a shape="rect" href="registry.html">Registry</a>:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<bean id="myCorrelationIdGenerator"
class="com.mycompany.MySimpleIdGenerator"/>
]]></script>
</div></div>
Modified: websites/production/camel/content/pax-logging.html
==============================================================================
--- websites/production/camel/content/pax-logging.html (original)
+++ websites/production/camel/content/pax-logging.html Thu Sep 14 19:25:46 2017
@@ -93,7 +93,7 @@
<h3 id="Pax-Logging-Dependencies">Dependencies</h3>
<p>Maven users need to add the following dependency to their
<code>pom.xml</code></p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-paxlogging</artifactId>
@@ -105,7 +105,7 @@
<h3 id="Pax-Logging-URIformat">URI format</h3>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
paxlogging:appender[?options]
]]></script>
</div></div>
@@ -134,7 +134,7 @@ paxlogging:appender[?options]
<h3 id="Pax-Logging-Exampleusage">Example usage</h3>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<route>
<from uri="paxlogging:camel"/>
<to uri="stream:out"/>
Modified: websites/production/camel/content/pdf-documentation-guide.html
==============================================================================
--- websites/production/camel/content/pdf-documentation-guide.html (original)
+++ websites/production/camel/content/pdf-documentation-guide.html Thu Sep 14
19:25:46 2017
@@ -153,7 +153,7 @@
<p>Use wiki markup similar to:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: plain; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
{html}<div class="table"><p class="caption">
Example Table
</p>{html}
@@ -180,7 +180,7 @@
<p>Use wiki markup similar to:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: plain; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
{html}<div class="figure"><p class="art">
{html}
!http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png!
{html}
</p><p class="caption">
@@ -206,7 +206,7 @@
<p>Use wiki markup similar to:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: plain; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
\{code:xml|title=Example}
<bean id="activemq"
class="org.apache.camel.component.jms.JmsComponent">
<property name="connectionFactory">
@@ -221,7 +221,7 @@
<p>To produce:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>Example</b></div><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<bean id="activemq"
class="org.apache.camel.component.jms.JmsComponent">
<property name="connectionFactory">
<bean
class="org.apache.activemq.ActiveMQConnectionFactory">
Modified: websites/production/camel/content/pgevent.html
==============================================================================
--- websites/production/camel/content/pgevent.html (original)
+++ websites/production/camel/content/pgevent.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2
id="PGEvent-PGEventComponent(PostgresSQLEvent)">PGEvent Component (PostgresSQL
Event)</h2><p>This is a component for Apache Camel which allows for
Producing/Consuming PostgreSQL events related to the LISTEN/NOTIFY commands
added since PostgreSQL 8.3.</p><p><span style="line-height: 1.4285715;">Maven
users will need to add the following dependency to their </span><code
style="line-height: 1.4285715;">pom.xml</code><span style="line-height:
1.4285715;"> for this component:</span></p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-pgevent</artifactId>
<version>x.x.x</version>
Modified: websites/production/camel/content/pluggable-class-resolvers.html
==============================================================================
--- websites/production/camel/content/pluggable-class-resolvers.html (original)
+++ websites/production/camel/content/pluggable-class-resolvers.html Thu Sep 14
19:25:46 2017
@@ -102,7 +102,7 @@
<p>We have provided easy configuration in Spring XML as you just need to
declare a spring bean with your custom resolver and Camel will pick it up
automatically.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<bean id="jbossresolver"
class="com.mycompany.jboss.JBossPackageScanClassResolver"/>
<camelContext id="camel"
xmlns="http://camel.apache.org/schema/spring">
@@ -123,7 +123,7 @@
<p>We have provided easy configuration in Spring XML as you just need to
declare a spring bean with your custom factory finder resolver and Camel will
pick it up automatically.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<bean id="jbossFactoryFinderResolver"
class="com.mycompany.jboss.JBossFactoryFinderResolver"/>
<camelContext id="camel"
xmlns="http://camel.apache.org/schema/spring">
Modified: websites/production/camel/content/pojo-consuming.html
==============================================================================
--- websites/production/camel/content/pojo-consuming.html (original)
+++ websites/production/camel/content/pojo-consuming.html Thu Sep 14 19:25:46
2017
@@ -129,7 +129,7 @@ from(uri).bean(theBean, "methodName
<p>The consumer above will only be created for the <a shape="rect"
href="camelcontext.html">CamelContext</a> that have the context id =
<code>camel-1</code>. You set this id in the XML tag:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<camelContext id="camel-1" ...>
]]></script>
</div></div>
@@ -194,7 +194,7 @@ public class MyService {
<p>If you define the bean in Spring XML or Blueprint, then you can configure
the property as follows:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<bean id="myService" class="com.foo.MyService">
<property name="serviceEndpoint"
value="activemq:queue:foo"/>
</bean>
Modified: websites/production/camel/content/printer.html
==============================================================================
--- websites/production/camel/content/printer.html (original)
+++ websites/production/camel/content/printer.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2
id="Printer-PrinterComponent">Printer Component</h2><p><strong>Available as of
Camel 2.1</strong></p><p>The <strong>printer</strong> component provides a way
to direct payloads on a route to a printer. Obviously the payload has to be a
formatted piece of payload in order for the component to appropriately print
it. The objective is to be able to direct specific payloads as jobs to a line
printer in a camel flow.</p><p>This component only supports a camel producer
endpoint.</p><p>The functionality allows for the payload to be printed on a
default printer, named local, remote or wirelessly linked printer using the
javax printing API under the covers.</p><p>Maven users will need to add the
following dependency to their <code>pom.xml</code> for this component:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-printer</artifactId>
<version>x.x.x</version>
Modified: websites/production/camel/content/properties.html
==============================================================================
--- websites/production/camel/content/properties.html (original)
+++ websites/production/camel/content/properties.html Thu Sep 14 19:25:46 2017
@@ -85,7 +85,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2
id="Properties-PropertiesComponent">Properties
Component</h2><p><strong>Available from Camel 2.3</strong></p><h3
id="Properties-URIformat">URI format</h3><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: bash; gutter: false; theme: Confluence"
type="syntaxhighlighter"><![CDATA[properties:key[?options]
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[properties:key[?options]
]]></script>
</div></div><p>Where <strong><code>key</code></strong> is the key for the
property to be looked up.</p><h3 id="Properties-Options">Options</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>cache</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Whether or not to cache loaded
properties.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>encoding</code></p></td><td colspan="1"
rowspan="1" class="conflu
enceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.14.3/2.15.1:</strong> The charset to
use when loading properties, such as
<strong><code>UTF-8</code></strong>.</p><p>The default charset is:
<strong><code>ISO-8859-1</code></strong>
(<strong><code>latin1</code></strong>).</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>fallbackToUnaugmentedProperty</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.9</strong> If
<strong><code>true</code></strong>, first attempt resolution of property name
augmented with <strong><code>propertyPrefix</code></strong> and
<strong><code>propertySuffix</code></strong> before falling back the plain
property nam
e specified.</p><p>If <strong><code>false</code></strong>, only the augmented
property name is searched.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>defaultFallbackEnabled</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.19</strong>:
If <strong><code>false</code></strong> the component will not attempt to
find a default for the key by looking after the colon
separator.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>ignoreMissingLocation</code></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong> Whether to
silently ignore if a location ca
nnot be located, such as a properties file not found.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>locations</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>A comma separated list of one or more
locations of property files to be loaded. Property resolution will use the
given property files exclusively. Any default location(s) are
ignored.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>prefixToken</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>{{</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.9</strong> This token is
used to mark the start of a property placeholder
definition.</p></td></tr><tr><td colspan="1" rows
pan="1" class="confluenceTd"><p><code>propertyPrefix</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9</strong> An
optional prefix that's <em>prepended</em> to each property name prior to
resolution.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>propertySuffix</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.9</strong> An optional
suffix that's <em>appended</em> to each property name prior to
resolution.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>suffixToken</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>String</code></
p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>}}<br
clear="none"></code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.9</strong> This token is used to mark
the end of a property placeholder definition.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>systemPropertiesMode</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>2</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.16</strong> The
mode to use for whether to resolve and use system
properties:</p><p><strong><code>0</code></strong> = never - JVM system
properties are never used.<br
clear="none"><strong><code>1</code></strong> = fallback - JVM system
properties are only used as fallback if no regular property with the key
exists.<br clear="none"><strong><code>2</code></strong> = override - JVM
system properties
are used if exists, otherwise the regular property will be used.</p><div
class="confluence-information-macro confluence-information-macro-warning"><p
class="title">Bridging Spring and Camel Property Placeholders</p><span
class="aui-icon aui-icon-small aui-iconfont-error
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When bridging to Spring's property
placeholder using
<strong><code>org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer</code></strong>
the configuration on
<strong><code>BridgePropertyPlaceholderConfigurer</code></strong> will take
precedence over the configuration on the
<strong><code>PropertiesComponent</code></strong>. </p></div></div></td></tr></tbody></table></div></div>
Modified: websites/production/camel/content/python.html
==============================================================================
--- websites/production/camel/content/python.html (original)
+++ websites/production/camel/content/python.html Thu Sep 14 19:25:46 2017
@@ -97,7 +97,7 @@
.to("seda:regularQueue");
]]></script>
</div></div><p>And a Spring DSL sample as well:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <route>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <route>
<from uri="direct:start"/>
<choice>
<when>
Modified: websites/production/camel/content/quartz.html
==============================================================================
--- websites/production/camel/content/quartz.html (original)
+++ websites/production/camel/content/quartz.html Thu Sep 14 19:25:46 2017
@@ -87,7 +87,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2 id="Quartz-QuartzComponent">Quartz
Component</h2><p>The <strong>quartz:</strong> component provides a scheduled
delivery of messages using the <a shape="rect" class="external-link"
href="http://www.quartz-scheduler.org/"; rel="nofollow">Quartz Scheduler 1.x
</a>. <br clear="none"> Each endpoint represents a different timer (in Quartz
terms, a Trigger and JobDetail).</p><div class="confluence-information-macro
confluence-information-macro-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 are using Quartz 2.x then
from Camel 2.12 onwards there is a <a shape="rect"
href="quartz2.html">Quartz2</a> component you should
use</p></div></div><p>Maven users will need to add the following dependency to
their <code>pom.xml</code> for this component:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent p
dl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-quartz</artifactId>
<version>x.x.x</version>
@@ -111,7 +111,7 @@ from("quartz://myGroup/myTimerName?
<p>To do this you can configure this in Spring XML as follows</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean id="quartz"
class="org.apache.camel.component.quartz.QuartzComponent">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean id="quartz"
class="org.apache.camel.component.quartz.QuartzComponent">
<property name="propertiesFile"
value="com/mycompany/myquartz.properties"/>
</bean>
]]></script>
@@ -119,7 +119,7 @@ from("quartz://myGroup/myTimerName?
<p>To do this you can configure this in Spring XML as follows</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean id="quartz"
class="org.apache.camel.component.quartz.QuartzComponent">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean id="quartz"
class="org.apache.camel.component.quartz.QuartzComponent">
<property name="startDelayedSeconds" value="5"/>
</bean>
]]></script>
Modified: websites/production/camel/content/quartz2.html
==============================================================================
--- websites/production/camel/content/quartz2.html (original)
+++ websites/production/camel/content/quartz2.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2
id="Quartz2-Quartz2Component">Quartz2 Component</h2><p><strong>Available as of
Camel 2.12.0</strong></p><p>The <strong>quartz2:</strong> component provides a
scheduled delivery of messages using the <a shape="rect" class="external-link"
href="http://www.quartz-scheduler.org/"; rel="nofollow">Quartz Scheduler 2.x
</a>. <br clear="none"> Each endpoint represents a different timer (in Quartz
terms, a Trigger and JobDetail).</p><p>Maven users will need to add the
following dependency to their <code>pom.xml</code> for this component:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-quartz2</artifactId>
<version>x.x.x</version>
@@ -109,7 +109,7 @@ quartz2://timerName?cron=expression
<p>To do this you can configure this in Spring XML as follows</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean id="quartz"
class="org.apache.camel.component.quartz2.QuartzComponent">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean id="quartz"
class="org.apache.camel.component.quartz2.QuartzComponent">
<property name="propertiesFile"
value="com/mycompany/myquartz.properties"/>
</bean>
]]></script>
@@ -117,7 +117,7 @@ quartz2://timerName?cron=expression
<p>To do this you can configure this in Spring XML as follows</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean id="quartz2"
class="org.apache.camel.component.quartz2.QuartzComponent">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean id="quartz2"
class="org.apache.camel.component.quartz2.QuartzComponent">
<property name="startDelayedSeconds" value="5"/>
</bean>
]]></script>
Modified: websites/production/camel/content/rabbitmq.html
==============================================================================
--- websites/production/camel/content/rabbitmq.html (original)
+++ websites/production/camel/content/rabbitmq.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2
id="RabbitMQ-RabbitMQComponent">RabbitMQ Component</h2><p><strong>Available as
of Camel 2.12</strong></p><p>The <strong>rabbitmq:</strong> component allows
you produce and consume messages from <a shape="rect" class="external-link"
href="http://www.rabbitmq.com/"; rel="nofollow">RabbitMQ</a> instances. Using
the RabbitMQ AMQP client, this component offers a pure RabbitMQ approach over
the generic <a shape="rect" class="external-link"
href="http://camel.apache.org/amqp.html";>AMQP</a> component.</p><p>Maven users
will need to add the following dependency to their <code>pom.xml</code> for
this component:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-rabbitmq</artifactId>
<version>x.x.x</version>
@@ -100,7 +100,7 @@
<p>See <a shape="rect" class="external-link"
href="http://www.rabbitmq.com/releases/rabbitmq-java-client/current-javadoc/com/rabbitmq/client/ConnectionFactory.html";
rel="nofollow">http://www.rabbitmq.com/releases/rabbitmq-java-client/current-javadoc/com/rabbitmq/client/ConnectionFactory.html</a>
and the AMQP specification for more information on connection options.</p><h2
id="RabbitMQ-Customconnectionfactory">Custom connection factory</h2><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean
id="customConnectionFactory"
class="com.rabbitmq.client.ConnectionFactory">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean
id="customConnectionFactory"
class="com.rabbitmq.client.ConnectionFactory">
<property name="host" value="localhost"/>
<property name="port" value="5672"/>
<property name="username" value="camel"/>
Modified: websites/production/camel/content/rcode.html
==============================================================================
--- websites/production/camel/content/rcode.html (original)
+++ websites/production/camel/content/rcode.html Thu Sep 14 19:25:46 2017
@@ -92,7 +92,7 @@
<h3 id="RCode-Dependency">Dependency</h3>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<dependency>
<groupId>org.apache-extras.camel-extra</groupId>
<artifactId>camel-rcode</artifactId>
Modified: websites/production/camel/content/recipientlist-annotation.html
==============================================================================
--- websites/production/camel/content/recipientlist-annotation.html (original)
+++ websites/production/camel/content/recipientlist-annotation.html Thu Sep 14
19:25:46 2017
@@ -109,7 +109,7 @@ public class RouterBean {
<p>For example if the above bean is configured in <a shape="rect"
href="spring.html">Spring</a> when using a
<strong><camelContext></strong> element as follows</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Modified: websites/production/camel/content/ref.html
==============================================================================
--- websites/production/camel/content/ref.html (original)
+++ websites/production/camel/content/ref.html Thu Sep 14 19:25:46 2017
@@ -120,7 +120,7 @@ ref:someName[?options]
<p>And you could have a list of endpoints defined in the <a shape="rect"
href="registry.html">Registry</a> such as:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<camelContext id="camel"
xmlns="http://activemq.apache.org/camel/schema/spring">
<endpoint id="normalOrder"
uri="activemq:order.slow"/>
<endpoint id="bigspenderOrder"
uri="activemq:order.high"/>
@@ -154,7 +154,7 @@ ref:someName[?options]
<p>You could, of course, have used the <code>ref</code> attribute instead:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<to ref="endpoint2"/>
]]></script>
</div></div>
Modified: websites/production/camel/content/release-guide.html
==============================================================================
--- websites/production/camel/content/release-guide.html (original)
+++ websites/production/camel/content/release-guide.html Thu Sep 14 19:25:46
2017
@@ -87,7 +87,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h1
id="ReleaseGuide-HowtocreateandannounceaCamelrelease.">How to create and
announce a Camel release.</h1><p>This release guide is based on the <a
shape="rect" class="external-link"
href="http://maven.apache.org/developers/release/apache-release.html";>General
guide for releasing Maven-based projects at Apache</a>, so be sure to check it
out before continuing and meet all prerequisites.</p><p><span style="font-size:
20.0px;line-height: 1.5;">Prerequisites</span></p><p>To prepare or perform a
release you MUST BE at least an Apache Camel committer.</p><ul><li>The
artifacts for each and every release must be SIGNED; your public key should be
added to the KEYS file</li><li>Your public key must also be cross-signed by
other Apache committers (this can be done at key signing parties at ApacheCon
for instance)</li><li>Make sure you have the correct maven configuration in
<code>~/.m2/settings.xml</code></li><li>From Camel 2.15 onwards we will require
to
use Maven [3.1.1,3.2.5)</li><li>From Camel 2.17 onwards we will require to
use Maven [3.2.5,3.3.x)</li><li>You may want to get familiar with the release
settings in the parent apache POM.</li><li>Make sure you are using Java 1.8 for
Apache Camel 2.18.0 and later (Java 1.7 for older versions).<br
clear="none"><br clear="none"></li></ul><h2 id="ReleaseGuide-Maven2Setup">Maven
2 Setup</h2><p>Before you deploy anything to the maven repository using Maven
2, you should configure your ~/.m2/settings.xml file so that the file
permissions of the deployed artifacts are group writable. If you do not do
this, other developers will not able to overwrite your SNAPSHOT releases with
newer versions. The settings follow the <a shape="rect" class="external-link"
href="http://maven.apache.org/developers/committer-settings.html";>guidelines
</a> used by the Maven project. Please pay particular attention to the <a
shape="rect" class="external-link"
href="http://maven.apache.org/guides/mini/guide-encryp
tion.html">password encryption recommendations</a>.</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<settings>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<settings>
...
<servers>
<!-- Per http://maven.apache.org/developers/committer-settings.html
-->
Modified: websites/production/camel/content/rmi.html
==============================================================================
--- websites/production/camel/content/rmi.html (original)
+++ websites/production/camel/content/rmi.html Thu Sep 14 19:25:46 2017
@@ -93,7 +93,7 @@
<p>Maven users will need to add the following dependency to their
<code>pom.xml</code> for this component:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-rmi</artifactId>
@@ -153,7 +153,7 @@ from(endpoint).to("pojo:bar");
<p>In XML DSL you can do as follows from <strong>Camel 2.7</strong>
onwards:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<camel:route>
<from
uri="rmi://localhost:37541/helloServiceBean?remoteInterfaces=org.apache.camel.example.osgi.HelloService"/>
<to uri="bean:helloServiceBean"/>
Modified: websites/production/camel/content/routebox.html
==============================================================================
--- websites/production/camel/content/routebox.html (original)
+++ websites/production/camel/content/routebox.html Thu Sep 14 19:25:46 2017
@@ -105,7 +105,7 @@
<p>Maven users will need to add the following dependency to their
<code>pom.xml</code> for this component:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-routebox</artifactId>
Modified: websites/production/camel/content/routepolicy.html
==============================================================================
--- websites/production/camel/content/routepolicy.html (original)
+++ websites/production/camel/content/routepolicy.html Thu Sep 14 19:25:46 2017
@@ -90,7 +90,7 @@
from("seda:foo").routePolicy(myPolicy).to("mock:result");
]]></script>
</div></div><p>In Spring XML its a bit different as follows using the
<strong><code>routePolicyRef</code></strong> attribute:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean id="myPolicy"
class="com.mycompany.MyRoutePolicy"/>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean id="myPolicy"
class="com.mycompany.MyRoutePolicy"/>
<route routePolicyRef="myPolicy">
<from uri="seda:foo"/>
@@ -98,7 +98,7 @@
</route>
]]></script>
</div></div><h3 id="RoutePolicy-ConfiguringPolicySets">Configuring Policy
Sets</h3><p><strong>Available as of Camel
2.7</strong></p><p><strong><code>RoutePolicy</code></strong> has been further
improved to allow addition of policy sets or a collection of policies that are
concurrently applied on a route. The addition of policies is done as
follows.</p><p>In the example below, the
route <strong><code>testRoute</code></strong> has
a <strong><code>startPolicy</code></strong>
and <strong><code>throttlePolicy</code></strong> applied concurrently.
Both policies are applied as necessary on the route.</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><
