Modified: websites/production/camel/content/message-bus.html
==============================================================================
--- websites/production/camel/content/message-bus.html (original)
+++ websites/production/camel/content/message-bus.html Thu Sep 11 10:19:20 2014
@@ -36,6 +36,16 @@
<![endif]-->
+ <link href='//camel.apache.org/styles/highlighter/styles/shCoreCamel.css'
rel='stylesheet' type='text/css' />
+ <link href='//camel.apache.org/styles/highlighter/styles/shThemeCamel.css'
rel='stylesheet' type='text/css' />
+ <script src='//camel.apache.org/styles/highlighter/scripts/shCore.js'
type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushJava.js'
type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushXml.js'
type='text/javascript'></script>
+
+ <script type="text/javascript">
+ SyntaxHighlighter.defaults['toolbar'] = false;
+ SyntaxHighlighter.all();
+ </script>
<title>
Apache Camel: Message Bus
@@ -75,19 +85,17 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3 id="MessageBus-MessageBus">Message
Bus</h3>
-
-<p>Camel supports the <a shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/PointToPointChannel.html";
rel="nofollow">Message Bus</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a>. You could view
Camel as a Message Bus itself as it allows producers and consumers to be
decoupled.</p>
-
-<p><img class="confluence-embedded-image confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/MessageBusSolution.gif";
data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessageBusSolution.gif";></p>
-
-<p>Folks often assume that a Message Bus is a JMS though so you may wish to
refer to the <a shape="rect" href="jms.html">JMS</a> component for traditional
MOM support.<br clear="none">
-Also worthy of note is the <a shape="rect" href="xmpp.html">XMPP</a> component
for supporting messaging over XMPP (Jabber)</p>
-
-<p>Of course there are also ESB products such as <a shape="rect"
class="external-link" href="http://servicemix.apache.org/home.html";>Apache
ServiceMix</a> which serve as full fledged message busses.<br clear="none">
-You can interact with <a shape="rect" class="external-link"
href="http://servicemix.apache.org/home.html";>Apache ServiceMix</a> from Camel
in many ways, but in particular you can use the <a shape="rect"
href="nmr.html">NMR</a> or <a shape="rect" href="jbi.html">JBI</a> component to
access the ServiceMix message bus directly.</p>
-
-<h4 id="MessageBus-UsingThisPattern">Using This Pattern</h4>
+<div class="wiki-content maincontent"><h3 id="MessageBus-MessageBus">Message
Bus</h3><p>Camel supports the <a shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/PointToPointChannel.html";
rel="nofollow">Message Bus</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a>. You could view
Camel as a Message Bus itself as it allows producers and consumers to be
decoupled.</p><p><img class="confluence-embedded-image
confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/MessageBusSolution.gif";
data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessageBusSolution.gif";></p><p>Folks
often assume that a Message Bus is a JMS though so you may wish to refer to
the <a shape="rect" href="jms.html">JMS</a> component for traditional MOM
support.<br clear="none"> Also worthy of note is the <a shape="rect"
href="xmpp.html">XMPP</a> component for supporting messaging over XMPP
(Jabber)</p><p
>Of course there are also ESB products such as <a shape="rect"
>class="external-link" href="http://servicemix.apache.org/home.html";>Apache
>ServiceMix</a> which serve as full fledged message busses.<br clear="none">
>You can interact with <a shape="rect" class="external-link"
>href="http://servicemix.apache.org/home.html";>Apache ServiceMix</a> from
>Camel in many ways, but in particular you can use the <a shape="rect"
>href="nmr.html">NMR</a> or <a shape="rect" href="jbi.html">JBI</a> component
>to access the ServiceMix message bus directly.</p><p> </p><h4
>id="MessageBus-Example">Example</h4><p>The following demonstrates how the
>Camel message bus can be used to communicate with consumers and
>producers</p><p><strong><br clear="none"></strong></p><p><strong>Using
>the <a shape="rect" href="fluent-builders.html">Fluent
>Builders</a></strong></p><div class="code panel pdl" style="border-width:
>1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[from("direct:start")
+ .pollEnrich("file:inbox?fileName=data.txt")
+ .to("jms:queue:foo");]]></script>
+</div></div><p> </p><p><strong><strong>Using the <a shape="rect"
href="spring-xml-extensions.html">Spring XML
Extensions</a></strong></strong></p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<route>
+ <from uri="direct:start"/>
+ <pollEnrich uri="file:inbox?fileName=data.txt"/>
+ <to uri="jms:queue:foo"/>
+</route>]]></script>
+</div></div><p></p><h4 id="MessageBus-UsingThisPattern">Using This Pattern</h4>
<p>If you would like to use this EIP Pattern then please read the <a
shape="rect" href="getting-started.html">Getting Started</a>, you may also find
the <a shape="rect" href="architecture.html">Architecture</a> useful
particularly the description of <a shape="rect"
href="endpoint.html">Endpoint</a> and <a shape="rect"
href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect"
href="examples.html">Examples</a> first before trying this pattern
out.</p></div>
</td>
Modified: websites/production/camel/content/message-channel.html
==============================================================================
--- websites/production/camel/content/message-channel.html (original)
+++ websites/production/camel/content/message-channel.html Thu Sep 11 10:19:20
2014
@@ -36,6 +36,17 @@
<![endif]-->
+ <link href='//camel.apache.org/styles/highlighter/styles/shCoreCamel.css'
rel='stylesheet' type='text/css' />
+ <link href='//camel.apache.org/styles/highlighter/styles/shThemeCamel.css'
rel='stylesheet' type='text/css' />
+ <script src='//camel.apache.org/styles/highlighter/scripts/shCore.js'
type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushJava.js'
type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushXml.js'
type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushPlain.js'
type='text/javascript'></script>
+
+ <script type="text/javascript">
+ SyntaxHighlighter.defaults['toolbar'] = false;
+ SyntaxHighlighter.all();
+ </script>
<title>
Apache Camel: Message Channel
@@ -75,18 +86,13 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3
id="MessageChannel-MessageChannel">Message Channel</h3>
-
-<p>Camel supports the <a shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/MessageChannel.html";
rel="nofollow">Message Channel</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a>. The Message
Channel is an internal implementation detail of the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html";>Endpoint</a>
interface and all interactions with the Message Channel are via the Endpoint
interfaces.</p>
-
-<p><img class="confluence-embedded-image confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/MessageChannelSolution.gif";
data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessageChannelSolution.gif";></p>
-
-<p>For more details see</p>
-
-<ul><li><a shape="rect" href="message.html">Message</a></li><li><a
shape="rect" href="message-endpoint.html">Message Endpoint</a></li></ul>
-
-
-<h4 id="MessageChannel-UsingThisPattern">Using This Pattern</h4>
+<div class="wiki-content maincontent"><h3
id="MessageChannel-MessageChannel">Message Channel</h3><p>Camel supports the <a
shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/MessageChannel.html";
rel="nofollow">Message Channel</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a>. The Message
Channel is an internal implementation detail of the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html";>Endpoint</a>
interface and all interactions with the Message Channel are via the Endpoint
interfaces.</p><p><img class="confluence-embedded-image
confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/MessageChannelSolution.gif";
data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessageChannelSolution.gif";></p><p><strong
style="font-size: 16.0px;line-height: 1.5625;"><br
clear="none"></strong></p><p><st
rong style="font-size: 16.0px;line-height: 1.5625;">Example</strong></p><p>In
JMS, Message Channels are represented by topics and queues such as the
following</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: text; gutter: false"
type="syntaxhighlighter"><![CDATA[jms:queue:foo]]></script>
+</div></div><p> </p><p>This message channel can be then used within the
<a shape="rect" href="jms.html">JMS</a> component</p><p><strong
style="line-height: 1.4285715;">Using the <a shape="rect"
href="fluent-builders.html">Fluent Builders</a></strong></p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[to("jms:queue:foo")]]></script>
+</div></div><p><strong><br clear="none"></strong></p><p><strong>Using
the <a shape="rect" href="spring-xml-extensions.html">Spring XML
Extensions</a></strong></p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<to
uri="jms:queue:foo"/>]]></script>
+</div></div><p> </p><p>For more details see</p><ul><li><a shape="rect"
href="message.html">Message</a></li><li><a shape="rect"
href="message-endpoint.html">Message Endpoint</a></li></ul><p></p><h4
id="MessageChannel-UsingThisPattern">Using This Pattern</h4>
<p>If you would like to use this EIP Pattern then please read the <a
shape="rect" href="getting-started.html">Getting Started</a>, you may also find
the <a shape="rect" href="architecture.html">Architecture</a> useful
particularly the description of <a shape="rect"
href="endpoint.html">Endpoint</a> and <a shape="rect"
href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect"
href="examples.html">Examples</a> first before trying this pattern
out.</p></div>
</td>
Modified: websites/production/camel/content/message-dispatcher.html
==============================================================================
--- websites/production/camel/content/message-dispatcher.html (original)
+++ websites/production/camel/content/message-dispatcher.html Thu Sep 11
10:19:20 2014
@@ -36,6 +36,16 @@
<![endif]-->
+ <link href='//camel.apache.org/styles/highlighter/styles/shCoreCamel.css'
rel='stylesheet' type='text/css' />
+ <link href='//camel.apache.org/styles/highlighter/styles/shThemeCamel.css'
rel='stylesheet' type='text/css' />
+ <script src='//camel.apache.org/styles/highlighter/scripts/shCore.js'
type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushJava.js'
type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushXml.js'
type='text/javascript'></script>
+
+ <script type="text/javascript">
+ SyntaxHighlighter.defaults['toolbar'] = false;
+ SyntaxHighlighter.all();
+ </script>
<title>
Apache Camel: Message Dispatcher
@@ -75,20 +85,41 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3
id="MessageDispatcher-MessageDispatcher">Message Dispatcher</h3>
-
-<p>Camel supports the <a shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/MessageDispatcher.html";
rel="nofollow">Message Dispatcher</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a> using various
approaches.</p>
-
-<p><img class="confluence-embedded-image confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/MessageDispatcher.gif";
data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessageDispatcher.gif";></p>
-
-<p>You can use a component like <a shape="rect" href="jms.html">JMS</a> with
selectors to implement a <a shape="rect"
href="selective-consumer.html">Selective Consumer</a> as the Message Dispatcher
implementation. Or you can use an <a shape="rect"
href="endpoint.html">Endpoint</a> as the Message Dispatcher itself and then use
a <a shape="rect" href="content-based-router.html">Content Based Router</a> as
the Message Dispatcher.</p>
-
-<h4 id="MessageDispatcher-SeeAlso">See Also</h4>
-
-<ul><li><a shape="rect" href="jms.html">JMS</a></li><li><a shape="rect"
href="selective-consumer.html">Selective Consumer</a></li><li><a shape="rect"
href="content-based-router.html">Content Based Router</a></li><li><a
shape="rect" href="endpoint.html">Endpoint</a></li></ul>
-
-
-<h4 id="MessageDispatcher-UsingThisPattern">Using This Pattern</h4>
+<div class="wiki-content maincontent"><h3
id="MessageDispatcher-MessageDispatcher">Message Dispatcher</h3><p>Camel
supports the <a shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/MessageDispatcher.html";
rel="nofollow">Message Dispatcher</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a> using various
approaches.</p><p><img class="confluence-embedded-image
confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/MessageDispatcher.gif";
data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessageDispatcher.gif";></p><p>You
can use a component like <a shape="rect" href="jms.html">JMS</a> with
selectors to implement a <a shape="rect"
href="selective-consumer.html">Selective Consumer</a> as the Message Dispatcher
implementation. Or you can use an <a shape="rect"
href="endpoint.html">Endpoint</a> as the Message Dispatcher itself and then use
a <a shape="rect" href="content-bas
ed-router.html">Content Based Router</a> as the Message
Dispatcher.</p><p> </p><h4
id="MessageDispatcher-Example">Example</h4><p>The following example
demonstrates <a shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/MessageDispatcher.html";
rel="nofollow">Message Dispatcher</a> pattern using the <a
shape="rect" href="competing-consumers.html">Competing Consumers</a>
functionality of the <a shape="rect"
href="jms.html">JMS</a> component to offload messages to a <a
shape="rect" href="content-based-router.html">Content Based Router</a> and
custom <a shape="rect"
href="processor.html">Processors</a> registered in the Camel <a
shape="rect" href="registry.html">Registry</a> running in separate threads
from originating consumer.</p><p> </p><p><strong>Using the <a
shape="rect" href="fluent-builders.html">Fluent Builders</a></strong></p><div
class="code panel pdl" style="border-widt
h: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[from("jms:queue:foo?concurrentConsumers=5")
+ .threads(5)
+ .choice()
+ .when(header("type").isEqualTo("A"))
+ .processRef("messageDispatchProcessorA")
+ .when(header("type").isEqualTo("B"))
+ .processRef("messageDispatchProcessorB")
+ .when(header("type").isEqualTo("C"))
+ .processRef("messageDispatchProcessorC")
+ .otherwise()
+
.to("jms:queue:invalidMessageType");]]></script>
+</div></div><p> </p><p><strong><strong>Using the <a shape="rect"
href="spring-xml-extensions.html">Spring XML
Extensions</a></strong></strong></p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<route>
+ <from uri="jms:queue:foo?concurrentConsumers=5"/>
+ <threads poolSize="5">
+ <choice>
+ <when>
+ <simple>${in.header.type} ==
'A'</simple>
+ <to
ref="messageDispatchProcessorA"/>
+ </when>
+ <when>
+ <simple>${in.header.type} ==
'B'</simple>
+ <to
ref="messageDispatchProcessorB"/>
+ </when>
+ <when>
+ <simple>${in.header.type} ==
'C'</simple>
+ <to
ref="messageDispatchProcessorC"/>
+ </when>
+ <otherwise>
+ <to
uri="jms:queue:invalidMessageType"/>
+ </choice>
+ </threads>
+</route>]]></script>
+</div></div><h4 id="MessageDispatcher-SeeAlso">See Also</h4><ul><li><a
shape="rect" href="jms.html">JMS</a></li><li><a shape="rect"
href="selective-consumer.html">Selective Consumer</a></li><li><a shape="rect"
href="content-based-router.html">Content Based Router</a></li><li><a
shape="rect" href="endpoint.html">Endpoint</a></li></ul><p> </p><p></p><h4
id="MessageDispatcher-UsingThisPattern">Using This Pattern</h4>
<p>If you would like to use this EIP Pattern then please read the <a
shape="rect" href="getting-started.html">Getting Started</a>, you may also find
the <a shape="rect" href="architecture.html">Architecture</a> useful
particularly the description of <a shape="rect"
href="endpoint.html">Endpoint</a> and <a shape="rect"
href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect"
href="examples.html">Examples</a> first before trying this pattern
out.</p></div>
</td>
Modified: websites/production/camel/content/message-endpoint.html
==============================================================================
--- websites/production/camel/content/message-endpoint.html (original)
+++ websites/production/camel/content/message-endpoint.html Thu Sep 11 10:19:20
2014
@@ -36,6 +36,16 @@
<![endif]-->
+ <link href='//camel.apache.org/styles/highlighter/styles/shCoreCamel.css'
rel='stylesheet' type='text/css' />
+ <link href='//camel.apache.org/styles/highlighter/styles/shThemeCamel.css'
rel='stylesheet' type='text/css' />
+ <script src='//camel.apache.org/styles/highlighter/scripts/shCore.js'
type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushJava.js'
type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushXml.js'
type='text/javascript'></script>
+
+ <script type="text/javascript">
+ SyntaxHighlighter.defaults['toolbar'] = false;
+ SyntaxHighlighter.all();
+ </script>
<title>
Apache Camel: Message Endpoint
@@ -75,20 +85,15 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3
id="MessageEndpoint-MessageEndpoint">Message Endpoint</h3>
-
-<p>Camel supports the <a shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/MessageEndpoint.html";
rel="nofollow">Message Endpoint</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a> using the <a
shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html";>Endpoint</a>
interface. </p>
-
-<p><img class="confluence-embedded-image confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/MessageEndpointSolution.gif";
data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessageEndpointSolution.gif";></p>
-
-<p>When using the <a shape="rect" href="dsl.html">DSL</a> to create <a
shape="rect" href="routes.html">Routes</a> you typically refer to Message
Endpoints by their <a shape="rect" href="uris.html">URIs</a> rather than
directly using the <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html";>Endpoint</a>
interface. Its then a responsibility of the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html";>CamelContext</a>
to create and activate the necessary Endpoint instances using the available <a
shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Component.html";>Component</a>
implementations.</p>
-
-<p>For more details see</p>
-
-<ul><li><a shape="rect" href="message.html">Message</a></li></ul>
-
-
-<h4 id="MessageEndpoint-UsingThisPattern">Using This Pattern</h4>
+<div class="wiki-content maincontent"><h3
id="MessageEndpoint-MessageEndpoint">Message Endpoint</h3><p>Camel supports the
<a shape="rect" class="external-link"
href="http://www.enterpriseintegrationpatterns.com/MessageEndpoint.html";
rel="nofollow">Message Endpoint</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a> using the <a
shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html";>Endpoint</a>
interface.</p><p><img class="confluence-embedded-image
confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/MessageEndpointSolution.gif";
data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessageEndpointSolution.gif";></p><p>When
using the <a shape="rect" href="dsl.html">DSL</a> to create <a shape="rect"
href="routes.html">Routes</a> you typically refer to Message Endpoints by their
<a shape="rect" href="uris.html">URIs</a> rather than di
rectly using the <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html";>Endpoint</a>
interface. Its then a responsibility of the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html";>CamelContext</a>
to create and activate the necessary Endpoint instances using the available <a
shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Component.html";>Component</a>
implementations.</p><h4 id="MessageEndpoint-Example">Example</h4><p>The
following example route demonstrates the use of a <a shape="rect"
href="https://cwiki.apache.org/confluence/display/SM/File";>File</a> Consumer
Endpoint and <a shape="rect" href="jms.html">JMS</a> Producer
Endpoint</p><p><strong><br clear="none"></strong></p><p><strong>Using
the <a shape="rect" href="fluent-builders.html">Fluent Build
ers</a></strong></p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[from("file://local/router/messages/foo")
+ .to("jms:queue:foo");]]></script>
+</div></div><p> </p><p><strong><strong>Using the <a shape="rect"
href="spring-xml-extensions.html">Spring XML
Extensions</a></strong></strong></p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<route>
+ <from uri="file://local/router/messages/foo"/>
+ <to uri="jms:queue:foo"/>
+</route>]]></script>
+</div></div><p> </p><p>For more details see</p><ul><li><a shape="rect"
href="message.html">Message</a><br clear="none"><br
clear="none"></li></ul><p></p><h4 id="MessageEndpoint-UsingThisPattern">Using
This Pattern</h4>
<p>If you would like to use this EIP Pattern then please read the <a
shape="rect" href="getting-started.html">Getting Started</a>, you may also find
the <a shape="rect" href="architecture.html">Architecture</a> useful
particularly the description of <a shape="rect"
href="endpoint.html">Endpoint</a> and <a shape="rect"
href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect"
href="examples.html">Examples</a> first before trying this pattern
out.</p></div>
</td>
Modified: websites/production/camel/content/metrics-component.html
==============================================================================
--- websites/production/camel/content/metrics-component.html (original)
+++ websites/production/camel/content/metrics-component.html Thu Sep 11
10:19:20 2014
@@ -217,7 +217,7 @@ from("direct:in")
</div></div><p>And from XML DSL you define a <bean> as follows:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[ <!-- use camel-metrics route policy to
gather metrics for all routes -->
<bean id="metricsRoutePolicyFactory"
class="org.apache.camel.component.metrics.routepolicy.MetricsRoutePolicyFactory"/>]]></script>
-</div></div><p>The <code>MetricsRoutePolicyFactory</code>
and <code>MetricsRoutePolicy</code> supports the following
options:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh">Name</th><th colspan="1" rowspan="1"
class="confluenceTh">Default</th><th colspan="1" rowspan="1"
class="confluenceTh">Description</th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">useJmx</td><td colspan="1" rowspan="1"
class="confluenceTd">false</td><td colspan="1" rowspan="1"
class="confluenceTd">Whether to report fine grained statistics to JMX by using
the <code>com.codahale.metrics.JmxReporter</code>.<br clear="none">Notice that
if JMX is enabled on <a shape="rect" href="camelcontext.html">CamelContext</a>
then a <code>MetricsRegistryService</code> mbean is enlisted under the services
type in the JMX tree. That mbean has a single operation to output the
statistics using json. Setting <code>useJmx</code> to true is onl
y needed if you want fine grained mbeans per statistics type.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">jmxDomain</td><td colspan="1"
rowspan="1" class="confluenceTd">org.apache.camel.metrics</td><td colspan="1"
rowspan="1" class="confluenceTd">The JMX domain name</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">prettyPrint</td><td colspan="1"
rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1"
class="confluenceTd">Whether to use pretty print when outputting statistics in
json format</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">metricsRegistry</td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd">Allow to use a shared
<code>com.codahale.metrics.MetricRegistry</code>. If none is provided then
Camel will create a shared instance used by the this
CamelContext.</td></tr></tbody></table></div><p> </p><p>From Java code tou
can get hold of the <code>com.
codahale.metrics.MetricRegistry</code><span> from the
<code>org.apache.camel.component.metrics.routepolicy.MetricsRegistryService</code>
as shown below:</span></p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+</div></div><p>The <code>MetricsRoutePolicyFactory</code>
and <code>MetricsRoutePolicy</code> supports the following
options:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh">Name</th><th colspan="1" rowspan="1"
class="confluenceTh">Default</th><th colspan="1" rowspan="1"
class="confluenceTh">Description</th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">useJmx</td><td colspan="1" rowspan="1"
class="confluenceTd">false</td><td colspan="1" rowspan="1"
class="confluenceTd">Whether to report fine grained statistics to JMX by using
the <code>com.codahale.metrics.JmxReporter</code>.<br clear="none">Notice that
if JMX is enabled on <a shape="rect" href="camelcontext.html">CamelContext</a>
then a <code>MetricsRegistryService</code> mbean is enlisted under the services
type in the JMX tree. That mbean has a single operation to output the
statistics using json. Setting <code>useJmx</code> to true is onl
y needed if you want fine grained mbeans per statistics type.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">jmxDomain</td><td colspan="1"
rowspan="1" class="confluenceTd">org.apache.camel.metrics</td><td colspan="1"
rowspan="1" class="confluenceTd">The JMX domain name</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">prettyPrint</td><td colspan="1"
rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1"
class="confluenceTd">Whether to use pretty print when outputting statistics in
json format</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">metricsRegistry</td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd">Allow to use a shared
<code>com.codahale.metrics.MetricRegistry</code>. If none is provided then
Camel will create a shared instance used by the this
CamelContext.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">rateUnit</td><td colspan="1" rowspan="1
" class="confluenceTd">TimeUnit.SECONDS</td><td colspan="1" rowspan="1"
class="confluenceTd">The unit to use for rate in the metrics reporter or when
dumping the statistics as json.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">durationUnit</td><td colspan="1" rowspan="1"
class="confluenceTd">TimeUnit.MILLISECONDS</td><td colspan="1" rowspan="1"
class="confluenceTd">The unit to use for duration in the metrics reporter or
when dumping the statistics as
json.</td></tr></tbody></table></div><p> </p><p>From Java code tou can get
hold of
the <code>com.codahale.metrics.MetricRegistry</code><span> from the
<code>org.apache.camel.component.metrics.routepolicy.MetricsRegistryService</code>
as shown below:</span></p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[MetricRegistryService registryService =
context.hasService(MetricsRegistryService.class);
if (registryService != null) {
MetricsRegistry registry = registryService.getMetricsRegistry();
Modified: websites/production/camel/content/mina2.html
==============================================================================
--- websites/production/camel/content/mina2.html (original)
+++ websites/production/camel/content/mina2.html Thu Sep 11 10:19:20 2014
@@ -85,142 +85,62 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="MINA2-MINA2Component">MINA 2
Component</h2>
-<p><strong>Available as of Camel 2.10</strong></p>
-
-<p>The <strong>mina2:</strong> component is a transport for working with <a
shape="rect" class="external-link" href="http://mina.apache.org/";>Apache MINA
2.x</a></p>
-
- <div class="aui-message success shadowed information-macro">
+<div class="wiki-content maincontent"><h2 id="MINA2-MINA2Component">MINA 2
Component</h2><p><strong>Available as of Camel 2.10</strong></p><p>The
<strong>mina2:</strong> component is a transport for working with <a
shape="rect" class="external-link" href="http://mina.apache.org/";>Apache MINA
2.x</a></p> <div class="aui-message success shadowed information-macro">
<span class="aui-icon icon-success">Icon</span>
<div class="message-content">
-
-<p>Favor using <a shape="rect" href="netty.html">Netty</a> as Netty is a much
more active maintained and popular project than Apache Mina currently is</p>
+ <p>Favor using <a shape="rect"
href="netty.html">Netty</a> as Netty is a much more active maintained and
popular project than Apache Mina currently is</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="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<dependency>
+<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="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-mina2</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
]]></script>
-</div></div>
-
-<h3 id="MINA2-URIformat">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-mina2:tcp://hostname[:port][?options]
+</div></div><h3 id="MINA2-URIformat">URI format</h3><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[mina2:tcp://hostname[:port][?options]
mina2:udp://hostname[:port][?options]
mina2:vm://hostname[:port][?options]
]]></script>
-</div></div>
-<p>You can specify a codec in the <a shape="rect"
href="registry.html">Registry</a> using the <strong>codec</strong> option. If
you are using TCP and no codec is specified then the <code>textline</code> flag
is used to determine if text line based codec or object serialization should be
used instead. By default the object serialization is used.</p>
-
-<p>For UDP if no codec is specified the default uses a basic
<code>ByteBuffer</code> based codec.</p>
-
-<p>The VM protocol is used as a direct forwarding mechanism in the same JVM.
</p>
-
-<p>A Mina producer has a default timeout value of 30 seconds, while it waits
for a response from the remote server.</p>
-
-<p>In normal use, <code>camel-mina</code> only supports marshalling the body
content—message headers and exchange properties are not sent.<br
clear="none">
-However, the option, <strong>transferExchange</strong>, does allow you to
transfer the exchange itself over the wire. See options below.</p>
-
-<p>You can append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p>
-
-<h3 id="MINA2-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> Default Value </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Description
</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>codec</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> You can refer to a named
<code>ProtocolCodecFactory</code> instance in your <a shape="rect"
href="registry.html">Registry</a> such as your Spring
<code>ApplicationContext</code>, which is then used for the marshalling.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>disconnect</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Whether or not to disconnect(clo
se) from Mina session right after use. Can be used for both consumer and
producer. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>textline</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Only used for TCP. If no codec
is specified, you can use this flag to indicate a text line based codec; if not
specified or the value is <code>false</code>, then Object Serialization is
assumed over TCP. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>textlineDelimiter</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>DEFAULT</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Only used for TCP
and if <strong>textline=true</strong>. Sets the text line delimiter to use.
Possible values are: <code>DEFAULT</code>, <code>AUTO</code>,
<code>WINDOWS</code>, <code>UNIX</code> or <code>MAC</code>. If none pr
ovided, Camel will use <code>DEFAULT</code>. This delimiter is used to mark
the end of text. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>sync</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Setting to set endpoint as one-way or
request-response. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>lazySessionCreation</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Sessions can be lazily created
to avoid exceptions, if the remote server is not up and running when the Camel
producer is started. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>timeout</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>30000</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> You c
an configure the timeout that specifies how long to wait for a response from a
remote server. The timeout unit is in milliseconds, so 60000 is 60 seconds. The
timeout is only used for Mina producer. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>encoding</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <em>JVM Default</em>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> You can configure
the encoding (a <a shape="rect" class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/api/java/nio/charset/Charset.html";
rel="nofollow">charset name</a>) to use for the TCP textline codec and the UDP
protocol. If not provided, Camel will use the <a shape="rect"
class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/api/java/nio/charset/Charset.html#defaultCharset()"
rel="nofollow">JVM default Charset</a>. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>transferExchange</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Only used for
TCP. You can transfer the exchange over the wire instead of just the body. The
following fields are transferred: In body, Out body, fault body, In headers,
Out headers, fault headers, exchange properties, exchange exception. This
requires that the objects are <em>serializable</em>. Camel will exclude any
non-serializable objects and log it at <code>WARN</code> level.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>minaLogger</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> You can enable the Apache MINA logging
filter. Apache MINA uses <code>slf4j</code> logging at <code>INFO</code> level
to log all input and output. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>filters</code> </p></
td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> You can set a
list of <a shape="rect" class="external-link"
href="http://mina.apache.org/iofilter.html";>Mina IoFilters</a> to register. The
<code>filters</code> can be specified as a comma-separate list of bean
references (e.g. <code>#filterBean1,#filterBean2</code>) where each bean must
be of type <code>org.apache.mina.common.IoFilter</code>. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>encoderMaxLineLength</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>-1</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Set the textline protocol encoder max line length. By
default the default value of Mina itself is used which are
<code>Integer.MAX_VALUE</code>. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>decoderMaxLineLength</code> </p></td><td colspan
="1" rowspan="1" class="confluenceTd"><p> <code>-1</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Set the textline protocol
decoder max line length. By default the default value of Mina itself is used
which are 1024. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>maximumPoolSize</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> 16 </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Number of worker threads in the worker pool for TCP
and UDP (UDP requires <strong>Camel 2.11.3/2.12.2</strong> onwards).
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>allowDefaultCodec</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> The mina component installs a default codec if both,
<code>codec</code> is <code>null</code> and <code>textline</code> is
<code>false</code>. Setting <code>allowDefau
ltCodec</code> to <code>false</code> prevents the mina component from
installing a default codec as the first element in the filter chain. This is
useful in scenarios where another filter must be the first in the filter chain,
like the SSL filter. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>disconnectOnNoReply</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> If sync is enabled then this
option dictates MinaConsumer if it should disconnect where there is no reply to
send back. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>noReplyLogLevel</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>WARN</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> If sync is enabled this option dictates
MinaConsumer which logging level to use when logging a there is no reply to
send back. Values are: <c
ode>FATAL, ERROR, INFO, DEBUG, OFF</code>. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>orderedThreadPoolExecutor</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 to use
ordered thread pool, to ensure events are processed orderly on the same
channel. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>sslContextParameters</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> SSL configuration using an
<code>org.apache.camel.util.jsse.SSLContextParameters</code> instance. See <a
shape="rect" class="unresolved" href="#">Using the JSSE Configuration
Utility</a>. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>autoStartTls</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 to
auto start SSL handshake. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="MINA2-Usingacustomcodec">Using a custom codec</h3>
-
-<p>See the Mina how to write your own codec. To use your custom codec with
<code>camel-mina</code>, you should register your codec in the <a shape="rect"
href="registry.html">Registry</a>; for example, by creating a bean in the
Spring XML file. Then use the <code>codec</code> option to specify the bean ID
of your codec. See <a shape="rect" href="hl7.html">HL7</a> that has a custom
codec.</p>
-
-<h3 id="MINA2-Samplewithsync=false">Sample with sync=false</h3>
-
-<p>In this sample, Camel exposes a service that listens for TCP connections on
port 6200. We use the <strong>textline</strong> codec. In our route, we create
a Mina consumer endpoint that listens on port 6200:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-from("mina2:tcp://localhost:" + port1 +
"?textline=true&sync=false").to("mock:result");
+</div></div><p>You can specify a codec in the <a shape="rect"
href="registry.html">Registry</a> using the <strong>codec</strong> option. If
you are using TCP and no codec is specified then the <code>textline</code> flag
is used to determine if text line based codec or object serialization should be
used instead. By default the object serialization is used.</p><p>For UDP if no
codec is specified the default uses a basic <code>ByteBuffer</code> based
codec.</p><p>The VM protocol is used as a direct forwarding mechanism in the
same JVM.</p><p>A Mina producer has a default timeout value of 30 seconds,
while it waits for a response from the remote server.</p><p>In normal use,
<code>camel-mina</code> only supports marshalling the body
content—message headers and exchange properties are not sent.<br
clear="none"> However, the option, <strong>transferExchange</strong>, does
allow you to transfer the exchange itself over the wire. See options
below.</p><p>You can append query options t
o the URI in the following format,
<code>?option=value&option=value&...</code></p><h3
id="MINA2-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>Default Value</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>codec</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>You can refer to a named
<code>ProtocolCodecFactory</code> instance in your <a shape="rect"
href="registry.html">Registry</a> such as your Spring
<code>ApplicationContext</code>, which is then used for the
marshalling.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>disconnect</code></p></td><td colspan="1" rowsp
an="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Whether or not to disconnect(close) from
Mina session right after use. Can be used for both consumer and
producer.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>textline</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Only used for TCP. If no codec is
specified, you can use this flag to indicate a text line based codec; if not
specified or the value is <code>false</code>, then Object Serialization is
assumed over TCP.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>textlineDelimiter</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>DEFAULT</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Only used for TCP and if
<strong>textline=true</strong>. Sets the text line delimiter to use. Pos
sible values are: <code>DEFAULT</code>, <code>AUTO</code>,
<code>WINDOWS</code>, <code>UNIX</code> or <code>MAC</code>. If none provided,
Camel will use <code>DEFAULT</code>. This delimiter is used to mark the end of
text.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>sync</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Setting to set endpoint as one-way or
request-response.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>lazySessionCreation</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Sessions can be lazily created
to avoid exceptions, if the remote server is not up and running when the Camel
producer is started.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>timeout</code></p></td><td colspan="1" rowspan=
"1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>You can configure the timeout that
specifies how long to wait for a response from a remote server. The timeout
unit is in milliseconds, so 60000 is 60 seconds. The timeout is only used for
Mina producer.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>encoding</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><em>JVM Default</em></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>You can configure the encoding
(a <a shape="rect" class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/api/java/nio/charset/Charset.html";
rel="nofollow">charset name</a>) to use for the TCP textline codec and the UDP
protocol. If not provided, Camel will use the <a shape="rect"
class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/api/java/nio/charset/Charset.html#defaultCharset()"
rel="nofollow">JVM default Charset</a>.</p></td>
</tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>transferExchange</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Only used for TCP. You can transfer the
exchange over the wire instead of just the body. The following fields are
transferred: In body, Out body, fault body, In headers, Out headers, fault
headers, exchange properties, exchange exception. This requires that the
objects are <em>serializable</em>. Camel will exclude any non-serializable
objects and log it at <code>WARN</code> level.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>minaLogger</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>You can enable the Apache MINA
logging filter. Apache MINA uses <code>slf4j</code> logging at
<code>INFO</code> level to log all input and output.</p><
/td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>filters</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>You can set a list of <a shape="rect"
class="external-link" href="http://mina.apache.org/iofilter.html";>Mina
IoFilters</a> to register. The <code>filters</code> can be specified as a
comma-separate list of bean references (e.g.
<code>#filterBean1,#filterBean2</code>) where each bean must be of type
<code>org.apache.mina.common.IoFilter</code>.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>encoderMaxLineLength</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Set the textline protocol
encoder max line length. By default the default value of Mina itself is used
which are <code>Integer.MAX_VALUE</code>.</p></td></tr><tr><td colspan="1"
rowspan="1
" class="confluenceTd"><p><code>decoderMaxLineLength</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Set the textline protocol
decoder max line length. By default the default value of Mina itself is used
which are 1024.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maximumPoolSize</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>16</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Number of worker threads in the worker pool for TCP and
UDP (UDP requires <strong>Camel 2.11.3/2.12.2</strong>
onwards).</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>allowDefaultCodec</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The mina component installs a default codec
if both, <code>codec</code> is <code>null</code> and <code
>textline</code> is <code>false</code>. Setting <code>allowDefaultCodec</code>
>to <code>false</code> prevents the mina component from installing a default
>codec as the first element in the filter chain. This is useful in scenarios
>where another filter must be the first in the filter chain, like the SSL
>filter.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>disconnectOnNoReply</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>If sync is enabled then this
>option dictates MinaConsumer if it should disconnect where there is no reply
>to send back.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>noReplyLogLevel</code></p></td><td colspan="1"
>rowspan="1" class="confluenceTd"><p><code>WARN</code></p></td><td colspan="1"
>rowspan="1" class="confluenceTd"><p>If sync is enabled this option dictates
>MinaConsumer which logging level to use when logg
ing a there is no reply to send back. Values are: <code>FATAL, ERROR, INFO,
DEBUG, OFF</code>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>orderedThreadPoolExecutor</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 to use ordered thread
pool, to ensure events are processed orderly on the same
channel.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>sslContextParameters</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>SSL configuration using an
<code>org.apache.camel.util.jsse.SSLContextParameters</code> instance. See <a
shape="rect" class="unresolved" href="#">Using the JSSE Configuration
Utility</a>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>autoStartTls</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 to auto start SSL
handshake.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><code>cachedAddress</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><code>true</code></td><td colspan="1" rowspan="1"
class="confluenceTd"><strong>Camel 2.14:</strong> Whether to create the
InetAddress once and reuse. Setting this to <code>false</code> allows to pickup
DNS changes in the network.</td></tr></tbody></table></div></div><h3
id="MINA2-Usingacustomcodec">Using a custom codec</h3><p>See the Mina how to
write your own codec. To use your custom codec with <code>camel-mina</code>,
you should register your codec in the <a shape="rect"
href="registry.html">Registry</a>; for example, by creating a bean in the
Spring XML file. Then use the <code>codec</code> option to specify the bean ID
of your codec. See <a shape="rect" href="hl7.html">HL7</a> that has a custom cod
ec.</p><h3 id="MINA2-Samplewithsync=false">Sample with sync=false</h3><p>In
this sample, Camel exposes a service that listens for TCP connections on port
6200. We use the <strong>textline</strong> codec. In our route, we create a
Mina consumer endpoint that listens on port 6200:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[from("mina2:tcp://localhost:" +
port1 + "?textline=true&sync=false").to("mock:result");
]]></script>
-</div></div>
-
-<p>As the sample is part of a unit test, we test it by sending some data to it
on port 6200.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-MockEndpoint mock = getMockEndpoint("mock:result");
+</div></div><p>As the sample is part of a unit test, we test it by sending
some data to it on port 6200.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[MockEndpoint mock =
getMockEndpoint("mock:result");
mock.expectedBodiesReceived("Hello World");
template.sendBody("mina2:tcp://localhost:" + port1 +
"?textline=true&sync=false", "Hello World");
assertMockEndpointsSatisfied();
]]></script>
-</div></div>
-
-<h3 id="MINA2-Samplewithsync=true">Sample with sync=true</h3>
-
-<p>In the next sample, we have a more common use case where we expose a TCP
service on port 6201 also use the textline codec. However, this time we want to
return a response, so we set the <code>sync</code> option to <code>true</code>
on the consumer.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-from("mina2:tcp://localhost:" + port2 +
"?textline=true&sync=true").process(new Processor() {
+</div></div><h3 id="MINA2-Samplewithsync=true">Sample with sync=true</h3><p>In
the next sample, we have a more common use case where we expose a TCP service
on port 6201 also use the textline codec. However, this time we want to return
a response, so we set the <code>sync</code> option to <code>true</code> on the
consumer.</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[from("mina2:tcp://localhost:" +
port2 + "?textline=true&sync=true").process(new Processor() {
public void process(Exchange exchange) throws Exception {
String body = exchange.getIn().getBody(String.class);
exchange.getOut().setBody("Bye " + body);
}
});
]]></script>
-</div></div>
-
-<p>Then we test the sample by sending some data and retrieving the response
using the <code>template.requestBody()</code> method. As we know the response
is a <code>String</code>, we cast it to <code>String</code> and can assert that
the response is, in fact, something we have dynamically set in our processor
code logic.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-String response =
(String)template.requestBody("mina2:tcp://localhost:" + port2 +
"?textline=true&sync=true", "World");
+</div></div><p>Then we test the sample by sending some data and retrieving the
response using the <code>template.requestBody()</code> method. As we know the
response is a <code>String</code>, we cast it to <code>String</code> and can
assert that the response is, in fact, something we have dynamically set in our
processor code logic.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[String response =
(String)template.requestBody("mina2:tcp://localhost:" + port2 +
"?textline=true&sync=true", "World");
assertEquals("Bye World", response);
]]></script>
-</div></div>
-
-<h3 id="MINA2-SamplewithSpringDSL">Sample with Spring DSL</h3>
-
-<p>Spring DSL can, of course, also be used for <a shape="rect"
href="mina.html">Mina</a>. In the sample below we expose a TCP server on port
5555:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
- <route>
+</div></div><h3 id="MINA2-SamplewithSpringDSL">Sample with Spring
DSL</h3><p>Spring DSL can, of course, also be used for <a shape="rect"
href="mina.html">MINA</a>. In the sample below we expose a TCP server on port
5555:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[ <route>
<from uri="mina2:tcp://localhost:5555?textline=true"/>
<to uri="bean:myTCPOrderHandler"/>
</route>
]]></script>
-</div></div>
-
-<p>In the route above, we expose a TCP server on port 5555 using the textline
codec. We let the Spring bean with ID, <code>myTCPOrderHandler</code>, handle
the request and return a reply. For instance, the handler bean could be
implemented as follows:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
- public String handleOrder(String payload) {
+</div></div><p>In the route above, we expose a TCP server on port 5555 using
the textline codec. We let the Spring bean with ID,
<code>myTCPOrderHandler</code>, handle the request and return a reply. For
instance, the handler bean could be implemented as follows:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[ public String handleOrder(String payload)
{
...
return "Order: OK"
}
]]></script>
-</div></div>
-
-
-<h3 id="MINA2-ClosingSessionWhenComplete">Closing Session When Complete</h3>
-
-<p>When acting as a server you sometimes want to close the session when, for
example, a client conversion is finished. To instruct Camel to close the
session, you should add a header with the key
<code>CamelMinaCloseSessionWhenComplete</code> set to a boolean
<code>true</code> value.</p>
-
-<p>For instance, the example below will close the session after it has written
the <code>bye</code> message back to the client:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-
from("mina2:tcp://localhost:8080?sync=true&textline=true").process(new
Processor() {
+</div></div><h3 id="MINA2-ClosingSessionWhenComplete">Closing Session When
Complete</h3><p>When acting as a server you sometimes want to close the session
when, for example, a client conversion is finished. To instruct Camel to close
the session, you should add a header with the key
<code>CamelMinaCloseSessionWhenComplete</code> set to a boolean
<code>true</code> value.</p><p>For instance, the example below will close the
session after it has written the <code>bye</code> message back to the
client:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from("mina2:tcp://localhost:8080?sync=true&textline=true").process(new
Processor() {
public void process(Exchange exchange) throws Exception {
String body = exchange.getIn().getBody(String.class);
exchange.getOut().setBody("Bye " + body);
@@ -228,19 +148,8 @@ assertEquals("Bye World", resp
}
});
]]></script>
-</div></div>
-
-<h3 id="MINA2-GettheIoSessionformessage">Get the IoSession for message</h3>
-
-<p>You can get the IoSession from the message header with this key
<code>Mina2Constants.MINA_IOSESSION</code>, and also get the local host address
with the key <code>Mina2Constants.MINA_LOCAL_ADDRESS</code> and remote host
address with the key <code>Mina2Constants.MINA_REMOTE_ADDRESS</code>.</p>
-
-<h3 id="MINA2-ConfiguringMinafilters">Configuring Mina filters</h3>
-
-<p>Filters permit you to use some Mina Filters, such as
<code>SslFilter</code>. You can also implement some customized filters. Please
note that <code>codec</code> and <code>logger</code> are also implemented as
Mina filters of type, <code>IoFilter</code>. Any filters you may define are
appended to the end of the filter chain; that is, after <code>codec</code> and
<code>logger</code>.</p>
-
-<h3 id="MINA2-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring
Camel</a></li><li><a shape="rect"
href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect"
href="getting-started.html">Getting Started</a></li></ul>
-<ul class="alternate"><li><a shape="rect" href="mina.html">Mina</a></li><li><a
shape="rect" href="netty.html">Netty</a></li></ul></div>
+</div></div><h3 id="MINA2-GettheIoSessionformessage">Get the IoSession for
message</h3><p>You can get the IoSession from the message header with this key
<code>Mina2Constants.MINA_IOSESSION</code>, and also get the local host address
with the key <code>Mina2Constants.MINA_LOCAL_ADDRESS</code> and remote host
address with the key <code>Mina2Constants.MINA_REMOTE_ADDRESS</code>.</p><h3
id="MINA2-ConfiguringMinafilters">Configuring Mina filters</h3><p>Filters
permit you to use some Mina Filters, such as <code>SslFilter</code>. You can
also implement some customized filters. Please note that <code>codec</code> and
<code>logger</code> are also implemented as Mina filters of type,
<code>IoFilter</code>. Any filters you may define are appended to the end of
the filter chain; that is, after <code>codec</code> and
<code>logger</code>.</p><p></p><h3 id="MINA2-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring
Camel</a></li><li><a shape="rect"
href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect"
href="getting-started.html">Getting Started</a></li></ul><ul
class="alternate"><li><a shape="rect" href="mina.html">MINA</a></li><li><a
shape="rect" href="netty.html">Netty</a></li></ul></div>
</td>
<td valign="top">
<div class="navigation">
![http://www.enterpriseintegrationpatterns.com/img/MessageBusSolution.gif"](http://www.enterpriseintegrationpatterns.com/img/MessageBusSolution.gif"){kind=link}
![http://www.enterpriseintegrationpatterns.com/img/MessageChannelSolution.gif"](http://www.enterpriseintegrationpatterns.com/img/MessageChannelSolution.gif"){kind=link}
![http://www.enterpriseintegrationpatterns.com/img/MessageDispatcher.gif"](http://www.enterpriseintegrationpatterns.com/img/MessageDispatcher.gif"){kind=link}
![http://www.enterpriseintegrationpatterns.com/img/MessageEndpointSolution.gif"](http://www.enterpriseintegrationpatterns.com/img/MessageEndpointSolution.gif"){kind=link}