Modified: websites/production/camel/content/gauth.html
==============================================================================
--- websites/production/camel/content/gauth.html (original)
+++ websites/production/camel/content/gauth.html Thu Sep 14 19:25:46 2017
@@ -118,7 +118,7 @@ gauth://name[?options]
<p>Some endpoint options such as <code>consumerKey</code>,
<code>consumerSecret</code> or <code>keyLoader</code> are usually set to the
same values on <code>gauth:authorize</code> and <code>gauth:upgrade</code>
endpoints. The <code>gauth</code> component allows to configure them on
component-level. These settings are then inherited by <code>gauth</code>
endpoints and need not be set redundantly in the endpoint URIs. Here are some
configuration examples.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>component configuration
for a registered web application using the HMAC-SHA1 signature
method</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="gauth"
class="org.apache.camel.component.gae.auth.GAuthComponent">
<property name="consumerKey"
value="example.appspot.com" />
<property name="consumerSecret" value="QAtA...HfQ"
/>
@@ -126,7 +126,7 @@ gauth://name[?options]
]]></script>
</div></div>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>component configuration
for an unregistered web application using the HMAC-SHA1 signature
method</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="gauth"
class="org.apache.camel.component.gae.auth.GAuthComponent">
<!-- Google will display a warning message on the authorization page
-->
<property name="consumerKey" value="anonymous" />
@@ -135,7 +135,7 @@ gauth://name[?options]
]]></script>
</div></div>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>component configuration
for a registered web application using the RSA-SHA1 signature
method</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="gauth"
class="org.apache.camel.component.gae.auth.GAuthComponent">
<property name="consumerKey"
value="ipfcloud.appspot.com" />
<property name="keyLoader" ref="jksLoader" />
@@ -207,7 +207,7 @@ public class GAuthRouteBuilder extends R
</div></div>
<p>The above example relies on the following component configuration.</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="gauth"
class="org.apache.camel.component.gae.auth.GAuthComponent">
<property name="consumerKey" value="anonymous" />
<property name="consumerSecret" value="anonymous"
/>
@@ -290,7 +290,7 @@ public class AccessExample {
<p>Maven users will need to add the following dependency to their
<code>pom.xml</code>.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>pom.xml</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[
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-gae</artifactId>
Modified: websites/production/camel/content/geocoder.html
==============================================================================
--- websites/production/camel/content/geocoder.html (original)
+++ websites/production/camel/content/geocoder.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="Geocoder-GeocoderComponent">Geocoder Component</h2><p><strong>Available as
of Camel 2.12</strong></p><p>The <strong>geocoder:</strong> component is used
for looking up geocodes (latitude and longitude) for a given address, or
reverse lookup. The component uses the <a shape="rect" class="external-link"
href="https://code.google.com/p/geocoder-java/"; rel="nofollow">Java API for
Google Geocoder</a> library.</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-geocoder</artifactId>
<version>x.x.x</version>
Modified: websites/production/camel/content/ghttp.html
==============================================================================
--- websites/production/camel/content/ghttp.html (original)
+++ websites/production/camel/content/ghttp.html Thu Sep 14 19:25:46 2017
@@ -131,7 +131,7 @@ ghttps://hostname[:port][/path][?options
<p>For receiving messages via the <code>ghttp</code> component, a
<code>CamelHttpTransportServlet</code> must be <a shape="rect"
href="gae.html#GAE-web-xml">configured and mapped</a> in the application's
<code>web.xml</code>. For example, to handle requests targeted at
<code>http://<appname>.appspot.com/camel/*</code> or <code><a
shape="rect" class="external-link" href="http://localhost/camel/*";
rel="nofollow">http://localhost/camel/*</a></code> (when using a local
development server) the following servlet mapping must be defined:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>web.xml</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[
...
<servlet>
<servlet-name>CamelServlet</servlet-name>
@@ -202,7 +202,7 @@ from(...)
<p>Maven users will need to add the following dependency to their
<code>pom.xml</code>. </p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>pom.xml</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[
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-gae</artifactId>
Modified: websites/production/camel/content/git.html
==============================================================================
--- websites/production/camel/content/git.html (original)
+++ websites/production/camel/content/git.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="Git-GitComponent">Git
Component</h2><p><strong>Available as of Camel
2.16</strong></p><p>The <strong>git:</strong> component allows you to
work with a generic Git repository. </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-git</artifactId>
<version>x.x.x</version>
Modified: websites/production/camel/content/github.html
==============================================================================
--- websites/production/camel/content/github.html (original)
+++ websites/production/camel/content/github.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="GitHub-GitHub">GitHub</h2><p><strong>Available as of Camel
2.15</strong></p><p>The GitHub component interacts with the GitHub API by
encapsulating <a shape="rect" class="external-link"
href="http://org.eclipse.egit.github.core"; rel="nofollow">egit-github</a>. It
currently provides polling for new pull requests, pull request comments, tags,
and commits.  It is also able to produce comments on pull requests, as
well as close the pull request entirely.</p><p>Rather than webhooks, this
endpoint relies on simple polling. Reasons include:</p><ul><li>Concern for
reliability/stability</li><li>The types of payloads we're polling aren't
typically large (plus, paging is available in the API)</li><li>The need to
support apps running somewhere not publicly accessible where a webhook would
fail</li></ul><p>Note that the GitHub API is fairly expansive.  Therefore,
this component could be easily expanded to provide additional interactions
.</p><p>Maven users will need to add the following dependency to their pom.xml
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-github</artifactId>
<version>${camel-version}</version>
Modified: websites/production/camel/content/glogin.html
==============================================================================
--- websites/production/camel/content/glogin.html (original)
+++ websites/production/camel/content/glogin.html Thu Sep 14 19:25:46 2017
@@ -183,7 +183,7 @@ public class GLoginTest {
<p>Maven users will need to add the following dependency to their
<code>pom.xml</code>. </p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>pom.xml</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[
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-gae</artifactId>
Modified: websites/production/camel/content/gmail.html
==============================================================================
--- websites/production/camel/content/gmail.html (original)
+++ websites/production/camel/content/gmail.html Thu Sep 14 19:25:46 2017
@@ -131,7 +131,7 @@ gmail://[email protected][?options]
<p>Maven users will need to add the following dependency to their
<code>pom.xml</code>. </p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>pom.xml</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[
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-gae</artifactId>
Modified: websites/production/camel/content/grape.html
==============================================================================
--- websites/production/camel/content/grape.html (original)
+++ websites/production/camel/content/grape.html Thu Sep 14 19:25:46 2017
@@ -102,7 +102,7 @@ CamelContext camelContext = grapeCamelCo
setBody().constant("org.apache.camel/camel-ftp/2.15.2").
to("grape:defaultMavenCoordinates");]]></script>
</div></div><h3 id="Grape-AddingtheGrapecomponenttotheproject">Adding the
Grape 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-grape</artifactId>
<version>x.y.z</version>
Modified: websites/production/camel/content/groovy-dsl.html
==============================================================================
--- websites/production/camel/content/groovy-dsl.html (original)
+++ websites/production/camel/content/groovy-dsl.html Thu Sep 14 19:25:46 2017
@@ -110,14 +110,14 @@
...
]]></script>
</div></div><h3 id="GroovyDSL-DevelopingwiththeGroovyDSL">Developing with the
Groovy DSL</h3><p>To be able to use the Groovy DSL in your camel routes you
need to add the a dependency on <strong>camel-groovy</strong> which implements
the Groovy DSL.</p><p>If you use Maven you can just add the following to your
pom.xml, substituting the version number for the latest & greatest release
(see the download page for the latest versions).</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-groovy</artifactId>
<version>2.11.0</version>
</dependency>
]]></script>
</div></div><p>Additionally you need to make sure that the Groovy classes will
be compiled. You can either use gmaven for this or, particularly with mixed
projects containing Java and Groovy code, you might want to use the <a
shape="rect" class="external-link"
href="http://groovy.codehaus.org/Groovy-Eclipse+compiler+plugin+for+Maven";
rel="nofollow">Groovy Eclipse compiler</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[ <plugin>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<compilerId>groovy-eclipse-compiler</compilerId>
@@ -132,7 +132,7 @@
</plugin>
]]></script>
</div></div><p>As Eclipse user, you might want to configure the Maven Eclipse
plugin in a way so that your project is set up correctly for using <a
shape="rect" class="external-link"
href="http://groovy.codehaus.org/Eclipse+Plugin"; rel="nofollow">Eclipse Plugin
for Groovy</a> when <code>mvn eclipse:eclipse</code> is executed:</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[ <plugin>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
Modified: websites/production/camel/content/groovy-renderer-user-guide.html
==============================================================================
--- websites/production/camel/content/groovy-renderer-user-guide.html (original)
+++ websites/production/camel/content/groovy-renderer-user-guide.html Thu Sep
14 19:25:46 2017
@@ -97,7 +97,7 @@
<p>Through <a shape="rect" href="web-console.html">Web Console</a>, you can
review every route in the <a shape="rect"
href="camelcontext.html">CamelContext</a>. After opening a route in your
browser, the URL may be <a shape="rect" class="external-link"
href="http://localhost:8080/routes/route1";
rel="nofollow">http://localhost:8080/routes/route1</a>, you can choose the edit
link with groovy to update it. A groovy renderer will turn the route into
groovy route definition. For example, after chooseing to edit a route defined
by the following XML:</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"
standalone="yes"?>
<route id="route1"
xmlns:ns2="http://camel.apache.org/schema/web"
xmlns="http://camel.apache.org/schema/spring">
<description>This is an example route which you can start, stop and
modify</description>
Modified: websites/production/camel/content/groovy.html
==============================================================================
--- websites/production/camel/content/groovy.html (original)
+++ websites/production/camel/content/groovy.html Thu Sep 14 19:25:46 2017
@@ -105,7 +105,7 @@
from("queue:foo").filter(groovy("request.lineItems.any { i
-> i.value > 100 }")).to("queue:bar")
]]></script>
</div></div><p>And the Spring DSL:</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="queue:foo"/>
<filter>
<groovy>request.lineItems.any { i -> i.value > 100
}</groovy>
Modified: websites/production/camel/content/gsec.html
==============================================================================
--- websites/production/camel/content/gsec.html (original)
+++ websites/production/camel/content/gsec.html Thu Sep 14 19:25:46 2017
@@ -89,7 +89,7 @@
<p>Securing GAE applications from unauthorized access is described in the <a
shape="rect" class="external-link"
href="http://code.google.com/appengine/docs/java/config/webxml.html#Security_and_Authentication";
rel="nofollow">Security and Authentication</a> section of the Google App
Engine documentation. Authorization constraints are declared in the <a
shape="rect" href="gae.html#GAE-Theweb.xml">web.xml</a>. This applies to Camel
applications as well. In the following example, the application is configured
to only allow authenticated users (in any role) to access the application.
Additionally, access to <code>/worker/*</code> URLs may only be done by users
in the admin role. By default, web hook URLs installed by the <a shape="rect"
href="gtask.html">gtask</a> component match the <code>/worker/*</code> pattern
and should not be accessed by normal users. With this authorization constraint,
only the task queuing service (which is always in the admin role) is allowed to
access the web ho
oks. For implementing custom, non-declarative authorization logic, Camel GAE
applications should use the <a shape="rect" class="external-link"
href="http://code.google.com/appengine/docs/java/users/overview.html";
rel="nofollow">Google Accounts Java API</a>.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>web.xml with
authorization constraint</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[
<web-app
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Modified: websites/production/camel/content/gtask.html
==============================================================================
--- websites/production/camel/content/gtask.html (original)
+++ websites/production/camel/content/gtask.html Thu Sep 14 19:25:46 2017
@@ -135,7 +135,7 @@ from(gtask:default) // receive message f
<p>This example requires the following servlet mapping.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>web.xml</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[
...
<servlet>
<servlet-name>CamelServlet</servlet-name>
@@ -156,7 +156,7 @@ from(gtask:default) // receive message f
<p>Maven users will need to add the following dependency to their
<code>pom.xml</code>. </p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>pom.xml</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[
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-gae</artifactId>
Modified: websites/production/camel/content/guava-eventbus.html
==============================================================================
--- websites/production/camel/content/guava-eventbus.html (original)
+++ websites/production/camel/content/guava-eventbus.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-guava-eventbus</artifactId>
Modified: websites/production/camel/content/guice.html
==============================================================================
--- websites/production/camel/content/guice.html (original)
+++ websites/production/camel/content/guice.html Thu Sep 14 19:25:46 2017
@@ -91,7 +91,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-guice</artifactId>
Modified: websites/production/camel/content/hazelcast-component.html
==============================================================================
--- websites/production/camel/content/hazelcast-component.html (original)
+++ websites/production/camel/content/hazelcast-component.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="HazelcastComponent-HazelcastComponent">Hazelcast
Component</h2><p><strong>Available as of Camel 2.7</strong></p><p>The
<strong>hazelcast:</strong> component allows you to work with the <a
shape="rect" class="external-link" href="http://www.hazelcast.com";
rel="nofollow">Hazelcast</a> distributed data grid / cache. Hazelcast is a in
memory data grid, entirely written in Java (single jar). It offers a great
palette of different data stores like map, multi map (same key, n values),
queue, list and atomic number. The main reason to use Hazelcast is its simple
cluster support. If you have enabled multicast on your network you can run a
cluster with hundred nodes with no extra configuration. Hazelcast can simply
configured to add additional features like n copies between nodes (default is
1), cache persistence, network configuration (if needed), near cache, enviction
and so on. For more information consult the Hazelcast documentation on <a shap
e="rect" class="external-link" href="http://www.hazelcast.com/docs.jsp";
rel="nofollow">http://www.hazelcast.com/docs.jsp</a>.</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-hazelcast</artifactId>
<version>x.x.x</version>
Modified:
websites/production/camel/content/hazelcast-idempotent-repository-tutorial.html
==============================================================================
---
websites/production/camel/content/hazelcast-idempotent-repository-tutorial.html
(original)
+++
websites/production/camel/content/hazelcast-idempotent-repository-tutorial.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="HazelcastIdempotentRepositoryTutorial-HazelcastIdempotentRepositoryTutorial">Hazelcast
Idempotent Repository Tutorial</h2><h3
id="HazelcastIdempotentRepositoryTutorial-Overview">Overview</h3><p>Apache
Camel enables you to integrate the Idempotent Consumer Pattern in a really
simple way. In this tutorial we will setup a cluster consisting of two OSGi
containers (Apache Karaf). Inside this both nodes we will deploy two equal
Camel bundles. This two bundles will receive a message from a REST interface,
send them via a Hazelcast SEDA queue and finally store it into a distributed
Hazelcast map. To avoid that a (equal) message will be consumed twice we're
using the idempotent repository implementation based on Hazelcast. This
implementation guarantees cluster wide that no message will be processed
twice.</p><h3 id="HazelcastIdempotentRepositoryTutorial-WhentoUse">When to
Use</h3><p>If you use camel in a clustered environment (2 nodes or more)
and you have to be sure that two equal messages never will be processed
twice.</p><h4 id="HazelcastIdempotentRepositoryTutorial-Whytouse">Why to
use</h4><p>Because you can create with very few effort a Idempotent Repository
over n nodes inside your Camel application.</p><h3
id="HazelcastIdempotentRepositoryTutorial-HowtoUse">How to Use</h3><p>We will
create a camel route with a restlet consumer and a hazelcast producer. These
routes will be deployed on the servers and form our cluster.</p><p><span
style="text-decoration: underline;">Preconsideration</span></p><p>The restlet
consumer will get XML strings that represent an invoice:</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[<Invoice id="${number}">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<Invoice id="${number}">
<Article name="foo"/>
</Invoice>
]]></script>
@@ -177,7 +177,7 @@ public class HazelcastIdempotenRepositor
}
]]></script>
</div></div><p>Our camel-context.xml</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[<?xml version="1.0"
encoding="UTF-8"?>
+<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"
@@ -192,7 +192,7 @@ public class HazelcastIdempotenRepositor
</beans>
]]></script>
</div></div><p>The pom.xml:</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[<?xml version="1.0"
encoding="UTF-8"?>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<?xml version="1.0"
encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
Modified: websites/production/camel/content/hbase.html
==============================================================================
--- websites/production/camel/content/hbase.html (original)
+++ websites/production/camel/content/hbase.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="hbase-HBaseComponent">HBase
Component</h2><p><strong>Available as of Camel 2.10</strong></p><p>This
component provides an idempotent repository, producers and consumers for <a
shape="rect" class="external-link" href="http://hbase.apache.org/";>Apache
HBase</a>.</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-hbase</artifactId>
<version>x.x.x</version>
@@ -94,7 +94,7 @@
</dependency>
]]></script>
</div></div><h3 id="hbase-ApacheHBaseOverview">Apache HBase
Overview</h3><p>HBase is an open-source, distributed, versioned,
column-oriented store modeled after Google's Bigtable: A Distributed Storage
System for Structured Data. You can use HBase when you need random, realtime
read/write access to your Big Data. More information at <a shape="rect"
class="external-link" href="http://hbase.apache.org";>Apache HBase</a>.</p><h3
id="hbase-CamelandHBase">Camel and HBase</h3><p>When using a datastore inside a
camel route, there is always the challenge of specifying how the camel message
will stored to the datastore. In document based stores things are more easy as
the message body can be directly mapped to a document. In relational databases
an ORM solution can be used to map properties to columns etc. In column based
stores things are more challenging as there is no standard way to perform that
kind of mapping.</p><p>HBase adds two additional challenges:</p><ul
class="alternate"><li>HBas
e groups columns into families, so just mapping a property to a column using a
name convention is just not enough.</li><li>HBase doesn't have the notion of
type, which means that it stores everything as byte[] and doesn't know if the
byte[] represents a String, a Number, a serialized Java object or just binary
data.</li></ul><p>To overcome these challenges, camel-hbase makes use of the
message headers to specify the mapping of the message to HBase columns. It also
provides the ability to use some camel-hbase provided classes that model HBase
data and can be easily convert to and from xml/json etc.<br clear="none">
Finally it provides the ability to the user to implement and use his own
mapping strategy.</p><p>Regardless of the mapping strategy camel-hbase will
convert a message into an org.apache.camel.component.hbase.model.HBaseData
object and use that object for its internal operations.</p><h3
id="hbase-Configuringthecomponent">Configuring the component</h3><p>The HBase
component
can be provided a custom HBaseConfiguration object as a property or it can
create an HBase configuration object on its own based on the HBase related
resources that are found on classpath.</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="hbase"
class="org.apache.camel.component.hbase.HBaseComponent">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <bean id="hbase"
class="org.apache.camel.component.hbase.HBaseComponent">
<property name="configuration" ref="config"/>
</bean>
]]></script>
@@ -108,7 +108,7 @@
<h4 id="hbase-PutOperations.">Put Operations.</h4><p>HBase is a column based
store, which allows you to store data into a specific column of a specific row.
Columns are grouped into families, so in order to specify a column you need to
specify the column family and the qualifier of that column. To store data into
a specific column you need to specify both the column and the row.</p><p>The
simplest scenario for storing data into HBase from a camel route, would be to
store part of the message body to specified HBase column.</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:in"/>
<!-- Set the HBase Row -->
<setHeader headerName="CamelHBaseRowId">
@@ -122,7 +122,7 @@
</route>
]]></script>
</div></div><p>The route above assumes that the message body contains an
object that has an id and value property and will store the content of value in
the HBase column myfamily:myqualifier in the row specified by id. If we needed
to specify more than one column/value pairs we could just specify additional
column mappings. Notice that you must use numbers from the 2nd header onwards,
eg RowId2, RowId3, RowId4, etc. Only the 1st header does not have the number
1.</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:in"/>
<!-- Set the HBase Row 1st column -->
<setHeader headerName="CamelHBaseRowId">
@@ -144,7 +144,7 @@
</route>
]]></script>
</div></div><p>It is important to remember that you can use uri options,
message headers or a combination of both. It is recommended to specify
constants as part of the uri and dynamic values as headers. If something is
defined both as header and as part of the uri, the header will be used.</p><h4
id="hbase-GetOperations.">Get Operations.</h4><p>A Get Operation is an
operation that is used to retrieve one or more values from a specified HBase
row. To specify what are the values that you want to retrieve you can just
specify them as part of the uri or as message headers.</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:in"/>
<!-- Set the HBase Row of the Get -->
<setHeader headerName="CamelHBaseRowId">
@@ -155,7 +155,7 @@
</route>
]]></script>
</div></div><p>In the example above the result of the get operation will be
stored as a header with name CamelHBaseValue.</p><h4
id="hbase-DeleteOperations.">Delete Operations.</h4><p>You can also you
camel-hbase to perform HBase delete operation. The delete operation will remove
an entire row. All that needs to be specified is one or more rows as part of
the message headers.</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:in"/>
<!-- Set the HBase Row of the Get -->
<setHeader headerName="CamelHBaseRowId">
@@ -165,14 +165,14 @@
</route>
]]></script>
</div></div><h4 id="hbase-ScanOperations.">Scan Operations.</h4><p>A scan
operation is the equivalent of a query in HBase. You can use the scan operation
to retrieve multiple rows. To specify what columns should be part of the result
and also specify how the values will be converted to objects you can use either
uri options or headers.</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:in"/>
<to
uri="hbase:mytable?operation=CamelHBaseScan&amp;family=myfamily&amp;qualifier=myqualifier&amp;valueType=java.lang.Long&amp;rowType=java.lang.String"/>
<to uri="log:out"/>
</route>
]]></script>
</div></div><p>In this case its probable that you also also need to specify a
list of filters for limiting the results. You can specify a list of filters as
part of the uri and camel will return only the rows that satisfy
<strong>ALL</strong> the filters. <br clear="none"> To have a filter that will
be aware of the information that is part of the message, camel defines the
ModelAwareFilter. This will allow your filter to take into consideration the
model that is defined by the message and the mapping strategy.<br clear="none">
When using a ModelAwareFilter camel-hbase will apply the selected mapping
strategy to the in message, will create an object that models the mapping and
will pass that object to the Filter.</p><p>For example to perform scan using as
criteria the message headers, you can make use of the
ModelAwareColumnMatchingFilter 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="direct:scan"/>
<!-- Set the Criteria -->
<setHeader headerName="CamelHBaseFamily">
Modified: websites/production/camel/content/hdfs.html
==============================================================================
--- websites/production/camel/content/hdfs.html (original)
+++ websites/production/camel/content/hdfs.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="HDFS-HDFSComponent">HDFS
Component</h2><p><strong>Available as of Camel 2.8</strong></p><p>The
<strong>hdfs</strong> component enables you to read and write messages from/to
an HDFS file system. HDFS is the distributed file system at the heart of <a
shape="rect" class="external-link"
href="http://hadoop.apache.org";>Hadoop</a>.</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-hdfs</artifactId>
<version>x.x.x</version>
Modified: websites/production/camel/content/hdfs2.html
==============================================================================
--- websites/production/camel/content/hdfs2.html (original)
+++ websites/production/camel/content/hdfs2.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="HDFS2-HDFS2Component">HDFS2
Component</h2><p><strong>Available as of Camel 2.13</strong></p><p>The
<strong>hdfs2</strong> component enables you to read and write messages from/to
an HDFS file system using Hadoop 2.x. HDFS is the distributed file system at
the heart of <a shape="rect" class="external-link"
href="http://hadoop.apache.org";>Hadoop</a>.</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-hdfs2</artifactId>
<version>x.x.x</version>
Modified: websites/production/camel/content/hibernate-example.html
==============================================================================
--- websites/production/camel/content/hibernate-example.html (original)
+++ websites/production/camel/content/hibernate-example.html Thu Sep 14
19:25:46 2017
@@ -112,7 +112,7 @@ The second route pickup the newly insert
<p>In the <code>camel-context.xml</code> file in the
<code>src/main/resources/META-INF/spring</code> folder we have the Spring XML
file to setup and configure the database and Hibernate, as well the <a
shape="rect" href="camelcontext.html">CamelContext</a>.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>Setting up
database</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[
<!-- this is the JDBC data source which uses an in-memory only Apache Derby
database -->
<bean id="dataSource"
class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close">
<property name="driverClassName"
value="org.apache.derby.jdbc.EmbeddedDriver"/>
@@ -126,7 +126,7 @@ The second route pickup the newly insert
<p>And in the same file we setup Hibernate. At first we have the Camel
Hibernate component, and then a number of beans to setup transactions. And then
the last bean setup the Hibernate session factory where we refer to the data
source and the hibernate mapping files, and any other hibernate configurations
we may need.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>Setting up
Hibernate</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[
<!-- setup the Camel hibernate component -->
<bean id="hibernate"
class="org.apacheextras.camel.component.hibernate.HibernateComponent">
<property name="sessionFactory"
ref="sessionFactory"/>
@@ -167,7 +167,7 @@ The second route pickup the newly insert
<p>And then in the same file we setup our Camel application. At first we have
a orderBean that we use in the routes to generate new orders and process orders
as well.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>Camel
application</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[
<!-- order bean is our business logic bean that creates new orders -->
<bean id="orderBean"
class="org.apacheextras.camel.examples.hibernate.OrderBean"/>
@@ -218,7 +218,7 @@ public class Order {
<p>The Order pojo is mapped to Hibernate using the mapping file
<code>Order.hbm.xml</code> which is located in the
<code>src/main/resources</code> directory of the example</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width: 1px;"><b>Hibernate mapping file to
Order pojo</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[
<hibernate-mapping>
<class
name="org.apacheextras.camel.examples.hibernate.Order"
schema="orders" table="incoming_order">
Modified: websites/production/camel/content/hipchat.html
==============================================================================
--- websites/production/camel/content/hipchat.html (original)
+++ websites/production/camel/content/hipchat.html Thu Sep 14 19:25:46 2017
@@ -117,7 +117,7 @@ public void configure() throws Exception
<h4 id="Hipchat-Dependencies"><span style="font-size: 16.0px;line-height:
1.5625;">Dependencies</span></h4><p>Maven users will need to add the following
dependency to their pom.xml.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeHeader panelHeader pdl"
style="border-bottom-width: 1px;"><b>pom.xml</b></div><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-hipchat</artifactId>
<version>${camel-version}</version>
Modified:
websites/production/camel/content/how-do-i-configure-the-default-maximum-cache-size-for-producercache-or-producertemplate.html
==============================================================================
---
websites/production/camel/content/how-do-i-configure-the-default-maximum-cache-size-for-producercache-or-producertemplate.html
(original)
+++
websites/production/camel/content/how-do-i-configure-the-default-maximum-cache-size-for-producercache-or-producertemplate.html
Thu Sep 14 19:25:46 2017
@@ -101,7 +101,7 @@ getCamelContext().getProperties().put(Ex
<p>And in Spring XML its done 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>
<properties>
<property key="CamelMaximumCachePoolSize"
value="50"/>
Modified:
websites/production/camel/content/how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.html
==============================================================================
---
websites/production/camel/content/how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.html
(original)
+++
websites/production/camel/content/how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.html
Thu Sep 14 19:25:46 2017
@@ -103,7 +103,7 @@ getCamelContext().getProperties().put(Ex
<p>And in Spring XML its done 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>
<properties>
<property key="CamelMaximumEndpointCacheSize"
value="500"/>
Modified:
websites/production/camel/content/how-do-i-enable-streams-when-debug-logging-messages-in-camel.html
==============================================================================
---
websites/production/camel/content/how-do-i-enable-streams-when-debug-logging-messages-in-camel.html
(original)
+++
websites/production/camel/content/how-do-i-enable-streams-when-debug-logging-messages-in-camel.html
Thu Sep 14 19:25:46 2017
@@ -118,7 +118,7 @@ You can customize whether Camel should l
<h4
id="HowdoIenablestreamswhendebugloggingmessagesinCamel-CustomizingfromSpringDSL">Customizing
from Spring DSL</h4>
<p>You add to the Camel properties the flag to log streams.</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>
<properties>
<property key="CamelLogDebugBodyStreams"
value="true"/>
Modified: websites/production/camel/content/how-do-i-name-my-routes.html
==============================================================================
--- websites/production/camel/content/how-do-i-name-my-routes.html (original)
+++ websites/production/camel/content/how-do-i-name-my-routes.html Thu Sep 14
19:25:46 2017
@@ -97,7 +97,7 @@ from("direct:start").routeId(&
<p>And in Spring XML using the <code>id</code> 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[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<route id="myRoute">
<from uri="direct:start"/>
<to uri="mock:bar"/>
Modified:
websites/production/camel/content/how-do-i-run-camel-using-java-webstart.html
==============================================================================
---
websites/production/camel/content/how-do-i-run-camel-using-java-webstart.html
(original)
+++
websites/production/camel/content/how-do-i-run-camel-using-java-webstart.html
Thu Sep 14 19:25:46 2017
@@ -99,7 +99,7 @@
<p>You need to configure your maven to not output the jar version attribute
(<code>outputJarVersion=false</code>) as started in this snippet</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[
<plugin>
<groupId>org.codehaus.mojo.webstart</groupId>
<artifactId>webstart-maven-plugin</artifactId>
@@ -136,7 +136,7 @@
<p>And a sample of the generated <strong>appl.jnlp</strong> 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[
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[
<jnlp .....>
.......
<resources>
Modified:
websites/production/camel/content/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.html
==============================================================================
---
websites/production/camel/content/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.html
(original)
+++
websites/production/camel/content/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.html
Thu Sep 14 19:25:46 2017
@@ -116,7 +116,7 @@ You can use a limit of 0 or negative to
<h4
id="HowdoIsetthemaxcharswhendebugloggingmessagesinCamel-CustomizingfromSpringDSL">Customizing
from Spring DSL</h4>
<p>You add to the Camel properties the limit. For example to limit at 500
chars:</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>
<properties>
<property key="CamelLogDebugBodyMaxChars"
value="500"/>
Modified:
websites/production/camel/content/how-to-avoid-sending-some-or-all-message-headers.html
==============================================================================
---
websites/production/camel/content/how-to-avoid-sending-some-or-all-message-headers.html
(original)
+++
websites/production/camel/content/how-to-avoid-sending-some-or-all-message-headers.html
Thu Sep 14 19:25:46 2017
@@ -108,7 +108,7 @@ from(...).removeHeaders("*", &
<p>To do (a similar thing) in XML DSL you simply do:</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[
<route>
<from uri="..."/>
<removeHeaders pattern="*"
excludePattern="header1|header2"/>
@@ -129,7 +129,7 @@ from(...).removeHeaders("Camel*&quo
<p>To do this in XML DSL you simply do:</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[
<route>
<from uri="..."/>
<removeHeaders pattern="Camel*"/>
Modified:
websites/production/camel/content/how-to-switch-the-cxf-consumer-between-http-and-https-without-touching-the-spring-configuration.html
==============================================================================
---
websites/production/camel/content/how-to-switch-the-cxf-consumer-between-http-and-https-without-touching-the-spring-configuration.html
(original)
+++
websites/production/camel/content/how-to-switch-the-cxf-consumer-between-http-and-https-without-touching-the-spring-configuration.html
Thu Sep 14 19:25:46 2017
@@ -90,7 +90,7 @@
<p>A simple Camel CXF Consumer configuration which use the http:conduit
configuration to enable SSL and an external properties file for all environment
specific configurations could looks like:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader
panelHeader pdl" style="border-bottom-width:
1px;"><b>bundle-context.xml</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[
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ctx="http://www.springframework.org/schema/context"
Modified:
websites/production/camel/content/how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html
==============================================================================
---
websites/production/camel/content/how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html
(original)
+++
websites/production/camel/content/how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html
Thu Sep 14 19:25:46 2017
@@ -90,7 +90,7 @@
<p>This can be done using the <a shape="rect" href="jetty.html">Jetty</a>
component 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[
<route>
<from
uri="jetty:http://0.0.0.0:8080/myapp?matchOnUriPrefix=true"/>
<to
uri="jetty:http://realserverhostname:8090/myapp?bridgeEndpoint=true&amp;throwExceptionOnFailure=false"/>
@@ -105,7 +105,7 @@ The option <code>matchOnUriPrefix</code>
<p>You can also use <a shape="rect" href="servlet.html">Servlet</a> instead of
<a shape="rect" href="jetty.html">Jetty</a>, for example:</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[
<route>
<from uri="servlet:myapp?matchOnUriPrefix=true"/>
<to
uri="http://realserverhostname:8090/myapp?bridgeEndpoint=true&amp;throwExceptionOnFailure=false"/>
Modified: websites/production/camel/content/http4.html
==============================================================================
--- websites/production/camel/content/http4.html (original)
+++ websites/production/camel/content/http4.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="HTTP4-HTTP4Component">HTTP4
Component</h2><p><strong>Available as of Camel
2.3</strong></p><p>The <strong><code>camel-http4</code></strong> component
provides HTTP based <a shape="rect" href="endpoint.html">endpoints</a> for
calling external HTTP resources (as a client to call external servers using
HTTP).</p><p>Maven users will need to add the following dependency to their
<strong><code>pom.xml</code></strong> 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-http4</artifactId>
<version>x.x.x</version>
@@ -105,7 +105,7 @@ HttpServletRequest response = exchange.g
.to("http4://oldhost");
]]></script>
</div></div><p><strong> Spring DSL</strong>:</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
xmlns="http://activemq.apache.org/camel/schema/spring">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<camelContext
xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
<from uri="direct:start"/>
<to uri="http4://oldhost"/>
@@ -136,7 +136,7 @@ HttpServletRequest response = exchange.g
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[.setHeader("CamelHttpMethod",
constant("POST"))
]]></script>
</div></div><p><strong> Spring DSL</strong>:</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
xmlns="http://activemq.apache.org/camel/schema/spring">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<camelContext
xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
<from uri="direct:start"/>
<setHeader headerName="CamelHttpMethod">
@@ -208,7 +208,7 @@ HttpComponent httpComponent = getContext
httpComponent.setSslContextParameters(scp);
]]></script>
</div></div><h6 id="HTTP4-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
@@ -267,7 +267,7 @@ httpComponent.setHttpClientConfigurer(ne
<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<to
uri="https4://myhostname.com:443/myURL?httpContext=myHttpContext"/>
]]></script>
</div></div><h5 id="HTTP4-UsingDifferentSSLContextParameters">Using
Different <code>SSLContextParameters</code></h5><p>The <a shape="rect"
href="http4.html">HTTP4</a> component only support one instance of
<strong><code>org.apache.camel.util.jsse.SSLContextParameters</code></strong>
per component. If you need to use two or more different instances, then you
need to setup multiple <a shape="rect" href="http4.html">HTTP4</a> components
as shown below. Where we have two components, each using their own instance of
<strong><code>sslContextParameters</code></strong> property.</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="http4-foo"
class="org.apache.camel.component.http4.HttpComponent">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean id="http4-foo"
class="org.apache.camel.component.http4.HttpComponent">
<property name="sslContextParameters"
ref="sslContextParams1"/>
<property name="x509HostnameVerifier"
ref="hostnameVerifier"/>
</bean>
Modified: websites/production/camel/content/hystrix-eip.html
==============================================================================
--- websites/production/camel/content/hystrix-eip.html (original)
+++ websites/production/camel/content/hystrix-eip.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="HystrixEIP-HystrixEIP">Hystrix
EIP</h2><p><strong>Available as of Camel 2.18</strong></p><p>The hystrix EIP
provides integration with Netflix <a shape="rect" class="external-link"
href="https://github.com/Netflix/Hystrix"; rel="nofollow">Hystrix</a> to be
used as circuit breaker in the Camel routes. Hystrix is a latency and fault
tolerance library designed to isolate points of access to remote systems,
services and 3rd party libraries, stop cascading failure and enable resilience
in complex distributed systems where failure is inevitable.</p><p>Maven users
will need to add the following dependency to
their <strong><code>pom.xml</code></strong> to use this EIP:</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-hystrix</artifactId>
<version>x.x.x</version><!-- use the same version as your
Camel core version -->
@@ -101,7 +101,7 @@
.end()
.to("mock:result");]]></script>
</div></div><p>And in XML DSL:</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
xmlns="http://camel.apache.org/schema/spring">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<camelContext
xmlns="http://camel.apache.org/schema/spring">
<route>
<from uri="direct:start"/>
<hystrix>
@@ -127,7 +127,7 @@
.end()
.to("mock:result");]]></script>
</div></div><p> </p><p>And in XML DSL:</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
xmlns="http://camel.apache.org/schema/spring">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<camelContext
xmlns="http://camel.apache.org/schema/spring">
<route>
<from uri="direct:start"/>
<hystrix>
@@ -143,7 +143,7 @@
</route>
</camelContext>]]></script>
</div></div><p>You can also configure hystrix globally and then refer to that
configuration:</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
xmlns="http://camel.apache.org/schema/spring">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<camelContext
xmlns="http://camel.apache.org/schema/spring">
Â
<!-- a shared config which you can refer to from all your hystrix EIPs
-->
<hystrixConfiguration id="sharedConfig"
executionTimeoutInMilliseconds="5000"
circuitBreakerSleepWindowInMilliseconds="10000"/>
Modified: websites/production/camel/content/ical.html
==============================================================================
--- websites/production/camel/content/ical.html (original)
+++ websites/production/camel/content/ical.html Thu Sep 14 19:25:46 2017
@@ -127,7 +127,7 @@ from("direct:ical-unmarshal")
<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-ical</artifactId>
Modified: websites/production/camel/content/ignite.html
==============================================================================
--- websites/production/camel/content/ignite.html (original)
+++ websites/production/camel/content/ignite.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="Ignite-CamelIgnitecomponent">Camel Ignite
component</h2><p><strong>Available as of Camel 2.17</strong></p><p><a
shape="rect" class="external-link" href="https://ignite.apache.org/";>Apache
Ignite</a> In-Memory Data Fabric is a high-performance, integrated and
distributed in-memory platform for computing and transacting on large-scale
data sets in real-time, orders of magnitude faster than possible with
traditional disk-based or flash technologies. It is designed to deliver
uncompromised performance for a wide set of in-memory computing use cases from
high performance computing, to the industry most advanced data grid, highly
available service grid, and streaming. See all <a shape="rect"
class="external-link"
href="https://ignite.apache.org/features.html";>features</a>.</p><p><span
class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img
class="confluence-embedded-image confluence-external-resource" height="250" sr
c="https://ignite.apache.org/images/apache-ignite.png";
data-image-src="https://ignite.apache.org/images/apache-ignite.png";></span></p><p>This
component offers seven endpoints to cover much of Ignite's
functionality:</p><ul><li>Ignite Cache.</li><li>Ignite Compute.</li><li>Ignite
Messaging.</li><li>Ignite Events.</li><li>Ignite Sets.</li><li>Ignite
Queues.</li><li>Ignite ID Generator.</li></ul><p><strong>To use this
component</strong>, add the following dependency to
your <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[<dependency>
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-ignite</artifactId>
<version>${camel.version}</version> <!-- use the same
version as your Camel core version -->
@@ -107,11 +107,11 @@
</div></div><p>This endpoint only supports producers.</p><h3
id="Ignite-Options.5">Options</h3><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh">Option</th><th colspan="1" rowspan="1"
class="confluenceTh">Type</th><th colspan="1" rowspan="1"
class="confluenceTh">Default value</th><th colspan="1" rowspan="1"
class="confluenceTh">Description</th><th colspan="1" rowspan="1"
class="confluenceTh">Compulsory</th><th colspan="1" rowspan="1"
class="confluenceTh">Consumer/producer</th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p class="p1"><code>operation</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p
class="p1"><code>IgniteQueueOperation</code> enum</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><pre class="p1">---</pre></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The operation to invoke on the Ignite
Queue.</p><p>Superseded by the <code>IgniteConstants.IGNITE_QUEUE_OPE
RATION</code> header in the IN message.</p><p>Possible values:
<code>CONTAINS<span class="s1" style="line-height: 1.42857;">,</span> ADD<span
class="s1" style="line-height: 1.42857;">,</span> SIZE<span class="s1"
style="line-height: 1.42857;">,</span> REMOVE<span class="s1"
style="line-height: 1.42857;">,</span> ITERATOR<span class="s1"
style="line-height: 1.42857;">,</span> CLEAR<span class="s1"
style="line-height: 1.42857;">,</span> RETAIN_ALL<span class="s1"
style="line-height: 1.42857;">,</span> ARRAY<span class="s1"
style="line-height: 1.42857;">,</span> DRAIN<span class="s1"
style="line-height: 1.42857;">,</span> ELEMENT<span class="s1"
style="line-height: 1.42857;">,</span> PEEK<span class="s1" style="line-height:
1.42857;">,</span> OFFER<span class="s1" style="line-height: 1.42857;">,</span>
POLL<span class="s1" style="line-height: 1.42857;">,</span> TAKE<span
class="s1" style="line-height: 1.42857;">,</span> PUT</code>.</p></td><td
colspan="1" rowspan="1" class="confluenceT
d">N</td><td colspan="1" rowspan="1" class="confluenceTd"><strong><span
style="color: rgb(0,128,0);">Producer</span></strong></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p
class="p1"><code>configuration</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><pre class="p1">CollectionConfiguration</pre></td><td
colspan="1" rowspan="1" class="confluenceTd">empty
<code>CollectionConfiguration</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>The configuration for this data structure. You can also
specify inner properties by using the <code>config.</code> prefix.</p><p>For
example: <code>?config.backups=4</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd">N</td><td colspan="1" rowspan="1"
class="confluenceTd"><strong><span style="color:
rgb(0,128,0);">Producer</span></strong></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><code>timeoutMillis</code></td><td colspan="1"
rowspan="1" class="confluenceTd"><code>Long</code><
/td><td colspan="1" rowspan="1" class="confluenceTd">---</td><td colspan="1"
rowspan="1" class="confluenceTd">The <span>timeout in milliseconds to use when
invoking the OFFER or POLL operations.</span></td><td colspan="1" rowspan="1"
class="confluenceTd">N</td><td colspan="1" rowspan="1"
class="confluenceTd"><strong><span style="color:
rgb(0,128,0);">Producer</span></strong></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><code>capacity</code></td><td colspan="1"
rowspan="1" class="confluenceTd"><code>int</code></td><td colspan="1"
rowspan="1" class="confluenceTd">--- (unbounded)</td><td colspan="1"
rowspan="1" class="confluenceTd">The queue capacity if you'd like to use a
bounded queue.</td><td colspan="1" rowspan="1" class="confluenceTd">N</td><td
colspan="1" rowspan="1" class="confluenceTd"><strong><span style="color:
rgb(0,128,0);">Producer</span></strong></td></tr></tbody></table></div><h3
id="Ignite-Headersused.4">Headers used</h3><p>This endpoint uses the follow
ing headers:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh">Header name</th><th colspan="1" rowspan="1"
class="confluenceTh">Constant</th><th colspan="1" rowspan="1"
class="confluenceTh">Expected type</th><th colspan="1" rowspan="1"
class="confluenceTh">Description</th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p
class="p1"><code>CamelIgniteQueueOperation</code></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><code>IgniteConstants.<span>IGNITE_QUEUE_OPERATION</span></code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>IgniteQueueOperation</code>
enum</td><td colspan="1" rowspan="1" class="confluenceTd"><p>Allows you to
dynamically change the queue operation.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><code>CamelIgniteQueueMaxElements</code></td><td
colspan="1" rowspan="1"
class="confluenceTd"><code>IgniteConstants.IGNITE_QUEUE_MAX_ELEMENTS</code></td><t
d colspan="1" rowspan="1" class="confluenceTd"><code>Integer or
int</code></td><td colspan="1" rowspan="1" class="confluenceTd">When invoking
the DRAIN operation, the amount of items to drain.</td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><code>CamelIgniteQueueTransferredCount</code></td><td
colspan="1" rowspan="1"
class="confluenceTd"><code><span><span>IgniteConstants.</span></span>IGNITE_QUEUE_TRANSFERRED_COUNT</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code><span>Integer or
int</span></code></td><td colspan="1" rowspan="1" class="confluenceTd">The
amount of items transferred as the result of the
DRAIN operation.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>CamelIgniteQueueTimeoutMillis</code></td><td
colspan="1" rowspan="1"
class="confluenceTd"><code><span><span>IgniteConstants.</span></span>IGNITE_QUEUE_TIMEOUT_MILLIS</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>Long or long</code></td><td
colspan
="1" rowspan="1" class="confluenceTd">Dynamically sets the timeout in
milliseconds to use when invoking the OFFER or POLL
operations. </td></tr></tbody></table></div><h2
id="Ignite-IDGEN:IgniteIDGeneratorendpoint">IDGEN: Ignite ID Generator
endpoint</h2><p>The Ignite ID Generator endpoint allows you to interact with <a
shape="rect" class="external-link"
href="https://apacheignite.readme.io/docs/id-generator"; rel="nofollow">Ignite
Atomic Sequences and ID Generators</a>.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ignite:idgen:sequenceName?option1=value1&option2=value2...]]></script>
</div></div><p>This endpoint only supports producers.</p><h3
id="Ignite-Options.6">Options</h3><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh">Option</th><th colspan="1" rowspan="1"
class="confluenceTh">Type</th><th colspan="1" rowspan="1"
class="confluenceTh">Default value</th><th colspan="1" rowspan="1"
class="confluenceTh">Description</th><th colspan="1" rowspan="1"
class="confluenceTh">Compulsory</th><th colspan="1" rowspan="1"
class="confluenceTh">Consumer/producer</th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p class="p1"><code>operation</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p
class="p1"><code>IgniteIdGenOperation enum</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><pre class="p1"><code>---</code></pre></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The operation to invoke on the
Ignite ID Generator.</p><p>Superseded by the <code>IgniteConsta
nts.IGNITE_IDGEN_OPERATION</code> header in the IN message.</p><p>Possible
values: <code>ADD_AND_GET<span class="s1" style="line-height:
1.42857;">,</span> GET<span class="s1" style="line-height: 1.42857;">,</span>
GET_AND_ADD<span class="s1" style="line-height: 1.42857;">,</span>
GET_AND_INCREMENT<span class="s1" style="line-height: 1.42857;">,</span>
INCREMENT_AND_GET</code>.</p></td><td colspan="1" rowspan="1"
class="confluenceTd">N</td><td colspan="1" rowspan="1"
class="confluenceTd"><strong><span style="color:
rgb(0,128,0);">Producer</span></strong></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p
class="p1"><code>configuration</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><pre class="p1">CollectionConfiguration</pre></td><td
colspan="1" rowspan="1" class="confluenceTd">empty
CollectionConfiguration</td><td colspan="1" rowspan="1"
class="confluenceTd"><p>The configuration for this data structure. You can also
specify inner properties by using t
he <code>config.</code> prefix.</p><p>For example:
<code>?config.backups=4</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd">N</td><td colspan="1" rowspan="1"
class="confluenceTd"><strong><span style="color:
rgb(0,128,0);">Producer</span></strong></td></tr></tbody></table></div><h2
id="Ignite-InitializingtheIgnitecomponent">Initializing the Ignite
component</h2><p>Each instance of the Ignite component is associated with an
underlying <code>org.apache.ignite.Ignite</code> instance. You can interact
with two Ignite clusters by initializing two instances of the Ignite component
and binding them to different <code>IgniteConfiguration</code>s. There are 3
ways to initialize the Ignite component:</p><ul><li>By passing in an existing
<code><span>org.apache.ignite.Ignite</span></code> instance. Here's an
example using Spring config:</li></ul><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 name="ignite"
class="org.apache.camel.component.ignite.IgniteComponent">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean name="ignite"
class="org.apache.camel.component.ignite.IgniteComponent">
<property name="ignite" ref="ignite" />
</bean>]]></script>
</div></div><ul><li>By passing in an <code>IgniteConfiguration</code>, either
constructed programmatically or through inversion of control (e.g. Spring,
Blueprint, etc.). Here's an example using Spring config:</li></ul><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 name="ignite"
class="org.apache.camel.component.ignite.IgniteComponent">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean name="ignite"
class="org.apache.camel.component.ignite.IgniteComponent">
<property name="igniteConfiguration">
<bean
class="org.apache.ignite.configuration.IgniteConfiguration">
[...]
@@ -119,7 +119,7 @@
</property>
</bean>]]></script>
</div></div><ul><li>By passing in a <code>URL</code>, <code>InputStream</code>
or <code>String</code> URL to a Spring-based configuration file. In all three
cases, you inject them in the same property called
<code>configurationResource</code>. Here's an example using Spring
config:</li></ul><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 name="ignite"
class="org.apache.camel.component.ignite.IgniteComponent">
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<bean name="ignite"
class="org.apache.camel.component.ignite.IgniteComponent">
<property name="configurationResource"
value="file:[...]/ignite-config.xml" />
</bean>]]></script>
</div></div><p><br clear="none">Additionally, if using Camel programmatically,
there are several convenience static methods in
<code>IgniteComponent</code> that return a component out of any of these
configuration
options:</p><ul><li><code>IgniteComponent#fromIgnite(Ignite)</code></li><li><code>IgniteComponent#fromConfiguration(IgniteConfiguration)</code></li><li><code>IgniteComponent#fromInputStream(InputStream)</code></li><li><code>IgniteComponent#fromUrl(URL)</code></li><li><code>IgniteComponent#<span
class="s2" style="font-family: monospace;line-height:
1.42857;">fromLocation(</span>String)</code></li></ul><div><span
style="font-family: monospace;"><br clear="none"></span></div><div>You may use
those methods to quickly create an <code>IgniteComponent</code> with your
chosen configuration technique.</div><h2 id="Ignite-Generaloptions">General
options</h2><p>All endpoints share the following options:</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th col
span="1" rowspan="1" class="confluenceTh">Option</th><th colspan="1"
rowspan="1" class="confluenceTh">Type</th><th colspan="1" rowspan="1"
class="confluenceTh">Default value</th><th colspan="1" rowspan="1"
class="confluenceTh">Description</th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>propagateIncomingBodyIfNoReturnValue</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>boolean</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>true</code></td><td
colspan="1" rowspan="1" class="confluenceTd">If the underlying Ignite operation
returns void (no return type), this flag determines whether the producer will
copy the IN body into the OUT body.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>treatCollectionsAsCacheObjects</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>boolean</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td
colspan="1" rowspan="1" class="confluen
ceTd">Some Ignite operations can deal with multiple elements at once, if
passed a Collection. Enabling this option will treat Collections as a single
object, invoking the operation variant for cardinality
1.</td></tr></tbody></table></div><h2 id="Ignite-OSGiSupportosgi-support">OSGi
Support<span class="confluence-anchor-link"
id="Ignite-osgi-support"></span></h2><div class="confluence-information-macro
confluence-information-macro-information"><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>Apache Ignite supports OSGi from
version 1.5.0.final onwards.</p></div></div><p><strong>NOTES when installing
on <a shape="rect" class="external-link"
href="http://karaf.apache.org/";>Apache
Karaf</a>:</strong></p><ol><li>Installing the camel-ignite feature will require
the <strong>Ignite feature repository</strong> to be present.</li><li>You must
have exported from the JRE (system bundle) some
low-level, non-standard packages that Ignite requires.</li></ol><p>Please
refer to the OSGi section in the <a shape="rect" class="external-link"
href="https://apacheignite.readme.io/docs/osgi-installation-in-karaf";
rel="nofollow">Ignite documentation</a> for more
information.</p><p></p><h3 id="Ignite-SeeAlso">See Also</h3>
![https://ignite.apache.org/images/apache-ignite.png"](https://ignite.apache.org/images/apache-ignite.png"){kind=link}