camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r891014 [2/3] - in /websites/production/camel/content: ./ cache/
Date Thu, 19 Dec 2013 02:22:12 GMT
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Thu Dec 19 02:22:12 2013
@@ -3914,22 +3914,22 @@ public class FilterTest extends Abstract
 @ContextConfiguration
 public class MyCamelTest {
 
-Ê Ê @Autowired
-Ê Ê protected CamelContext camelContext;
+    @Autowired
+    protected CamelContext camelContext;
 
-Ê Ê @EndpointInject(uri = "mock:foo")
-Ê Ê protected MockEndpoint foo;
+    @EndpointInject(uri = "mock:foo")
+    protected MockEndpoint foo;
 
 
     @Test
     @DirtiesContext
-Ê Ê public void testMocksAreValid() throws Exception {
-        ...Ê Ê Ê Ê
+    public void testMocksAreValid() throws Exception {
+        ...       
 
-Ê Ê Ê Ê foo.message(0).header("bar").isEqualTo("ABC");
+        foo.message(0).header("bar").isEqualTo("ABC");
 
-Ê Ê Ê Ê MockEndpoint.assertIsSatisfied(camelContext);
-Ê Ê }
+        MockEndpoint.assertIsSatisfied(camelContext);
+    }
 }
 ]]></script>
 </div></div>
@@ -4749,11 +4749,11 @@ While not actual tutorials you might fin
 
 <p>This tutorial aims to guide the reader through the stages of creating a project which uses Camel to facilitate the routing of messages from a JMS queue to a <a shape="rect" class="external-link" href="http://www.springramework.org" rel="nofollow">Spring</a> service.  The route works in a synchronous fashion returning a response to the client.</p>
 <style type="text/css">/*<![CDATA[*/
-div.rbtoc1387228660619 {padding: 0px;}
-div.rbtoc1387228660619 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1387228660619 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1387419554386 {padding: 0px;}
+div.rbtoc1387419554386 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1387419554386 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style><div class="toc-macro rbtoc1387228660619">
+/*]]>*/</style><div class="toc-macro rbtoc1387419554386">
 <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting with JMS</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Preface">Preface</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-About">About</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-CreatetheCamelProject">Create the Camel Project</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-UpdatethePOMwithDependencies">Update the POM with Dependencies</a></li></ul>
 </li><li><a shape="rect" href="#Tutorial-JmsRemoting-WritingtheServer">Writing the Server</a>
@@ -7094,11 +7094,11 @@ So we completed the last piece in the pi
 
 
 <style type="text/css">/*<![CDATA[*/
-div.rbtoc1387228660765 {padding: 0px;}
-div.rbtoc1387228660765 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1387228660765 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1387419554763 {padding: 0px;}
+div.rbtoc1387419554763 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1387419554763 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style><div class="toc-macro rbtoc1387228660765">
+/*]]>*/</style><div class="toc-macro rbtoc1387419554763">
 <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis 1.4 with Apache Camel</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Introduction">Introduction</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-SettinguptheprojecttorunAxis">Setting up the project to run Axis</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Maven2">Maven 2</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-wsdl">wsdl</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-ConfiguringAxis">Configuring Axis</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-RunningtheExample">Running the Example</a></li></ul>
@@ -12732,7 +12732,7 @@ from(&quot;direct:start&quot;).marshal()
 <p>In this example we unmarshal&#160;a zipped&#160;payload from an ActiveMQ queue called MY_QUEUE&#160;to its original format,&#160;and forward it for&#160;processing&#160;to the UnZippedMessageProcessor. Note that the compression Level employed during the marshalling should be identical to the one employed during unmarshalling to avoid errors.</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(&quot;activemq:queue:MY_QUEUE&quot;).unmarshal().zip().process(new UnZippedMessageProcessor());Ê
+from(&quot;activemq:queue:MY_QUEUE&quot;).unmarshal().zip().process(new UnZippedMessageProcessor()); 
 ]]></script>
 </div></div>
 
@@ -21722,54 +21722,23 @@ from(&quot;direct:start&quot;).choice()
 <h4 id="BookInOnePage-UsingThisPattern.46">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>
-<h3 id="BookInOnePage-WireTap">Wire Tap</h3>
-
-<p><a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/WireTap.html" rel="nofollow">Wire Tap</a> (from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a>) allows you to route messages to a separate location while they are being forwarded to the ultimate destination.</p>
-
-<p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif" data-image-src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif"></p>
-
-    <div class="aui-message hint shadowed information-macro">
+<h3 id="BookInOnePage-WireTap">Wire Tap</h3><p><a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/WireTap.html" rel="nofollow">Wire Tap</a> (from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a>) allows you to route messages to a separate location while they are being forwarded to the ultimate destination.</p><p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif" data-image-src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif"></p>    <div class="aui-message hint shadowed information-macro">
                     <p class="title">Streams</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">
-                            
-<p>If you <a shape="rect" href="wire-tap.html">Wire Tap</a> a stream message body then you should consider enabling <a shape="rect" href="stream-caching.html">Stream Caching</a> to ensure the message body can be read at each endpoint. See more details at <a shape="rect" href="stream-caching.html">Stream Caching</a>.  </p>
+                            <p>If you <a shape="rect" href="wire-tap.html">Wire Tap</a> a stream message body then you should consider enabling <a shape="rect" href="stream-caching.html">Stream caching</a> to ensure the message body can be read at each endpoint. See more details at <a shape="rect" href="stream-caching.html">Stream caching</a>.</p>
                     </div>
     </div>
-
-
-<h3 id="BookInOnePage-Options.21">Options</h3>
-
-<div class="confluenceTableSmall">
+<h3 id="BookInOnePage-Options.21">Options</h3><div class="confluenceTableSmall">
 <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>uri</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The URI of the endpoint to which the wire-tapped message will be sent. You should use either <code>uri</code> or <code>ref</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>ref</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Reference identifier of the endpoint to which the wire-tapped message will be sent. You should use either <code>uri</code> or <code>ref</code>. </p></td></tr><tr><td colspan="1" rows
 pan="1" class="confluenceTd"><p> <code>executorServiceRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Reference identifier of a custom <a shape="rect" href="threading-model.html" title="Threading Model">Thread Pool</a> to use when processing the wire-tapped messages. If not set, Camel will use a default thread pool. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>processorRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Reference identifier of a custom <a shape="rect" href="processor.html" title="Processor">Processor</a> to use for creating a new message (e.g., the "send a new message" mode). See below. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>copy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p><
 /td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3</strong>: Whether to copy the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> before wire-tapping the message. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>onPrepareRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong> Reference identifier of a custom <a shape="rect" href="processor.html" title="Processor">Processor</a> to prepare the copy of the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> to be wire-tapped. This allows you to do any custom logic, such as deep-cloning the message payload. </p></td></tr></tbody></table>
-</div>
-
-
-<h3 id="BookInOnePage-WireTapthreadpool">WireTap thread pool</h3>
-
-<p>The <a shape="rect" href="wire-tap.html">Wire Tap</a> uses a thread pool to process the tapped messages. This thread pool will by default use the settings detailed at <a shape="rect" href="threading-model.html">Threading Model</a>.  In particular, when the pool is exhausted (with all threads utilized), further wiretaps will be executed synchronously by the calling thread.  To remedy this, you can configure an explicit thread pool on the <a shape="rect" href="wire-tap.html">Wire Tap</a> having either a different rejection policy, a larger worker queue, or more worker threads.</p>
-
-<h3 id="BookInOnePage-WireTapnode">WireTap node</h3>
-
-<p>Camel's Wire Tap node supports two flavors when tapping an <a shape="rect" href="exchange.html">Exchange</a>:</p>
-
-<p>-With the traditional Wire Tap, Camel will copy the original <a shape="rect" href="exchange.html">Exchange</a> and set its <a shape="rect" href="exchange-pattern.html">Exchange Pattern</a> to <strong>InOnly</strong>, as we want the tapped <a shape="rect" href="exchange.html">Exchange</a> to be sent in a <em>fire and forget</em> style. The tapped <a shape="rect" href="exchange.html">Exchange</a> is then sent in a separate thread so it can run in parallel with the original.</p>
-
-<p>-Camel also provides an option of sending a new <a shape="rect" href="exchange.html">Exchange</a> allowing you to populate it with new values.</p>
-
-<h4 id="BookInOnePage-Sendingacopy(traditionalwiretap)">Sending a copy (traditional wiretap)</h4>
-<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">
+</div><h3 id="BookInOnePage-WireTapthreadpool">WireTap thread pool</h3><p>The <a shape="rect" href="wire-tap.html">Wire Tap</a> uses a thread pool to process the tapped messages. This thread pool will by default use the settings detailed at <a shape="rect" href="threading-model.html">Threading Model</a>. In particular, when the pool is exhausted (with all threads utilized), further wiretaps will be executed synchronously by the calling thread. To remedy this, you can configure an explicit thread pool on the <a shape="rect" href="wire-tap.html">Wire Tap</a> having either a different rejection policy, a larger worker queue, or more worker threads.</p><h3 id="BookInOnePage-WireTapnode">WireTap node</h3><p>Camel's Wire Tap node supports two flavors when tapping an <a shape="rect" href="exchange.html">Exchange</a>:</p><p>-With the traditional Wire Tap, Camel will copy the original <a shape="rect" href="exchange.html">Exchange</a> and set its <a shape="rect" href="exchange-pattern.html">E
 xchange Pattern</a> to <strong>InOnly</strong>, as we want the tapped <a shape="rect" href="exchange.html">Exchange</a> to be sent in a <em>fire and forget</em> style. The tapped <a shape="rect" href="exchange.html">Exchange</a> is then sent in a separate thread so it can run in parallel with the original.</p><p>-Camel also provides an option of sending a new <a shape="rect" href="exchange.html">Exchange</a> allowing you to populate it with new values.</p><h4 id="BookInOnePage-Sendingacopy(traditionalwiretap)">Sending a copy (traditional wiretap)</h4><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(&quot;direct:start&quot;)
     .to(&quot;log:foo&quot;)
     .wireTap(&quot;direct:tap&quot;)
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<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">
+</div></div><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[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
@@ -21778,16 +21747,7 @@ from(&quot;direct:start&quot;)
     &lt;to uri=&quot;mock:result&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<h4 id="BookInOnePage-Sendinganew">Sending a new <a shape="rect" href="exchange.html">Exchange</a></h4>
-<p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent Builders</a></strong><br clear="none">
-Camel supports either a processor or an <a shape="rect" href="expression.html">Expression</a> to populate the new <a shape="rect" href="exchange.html">Exchange</a>. Using a processor gives you full power over how the <a shape="rect" href="exchange.html">Exchange</a> is populated as you can set properties, headers, et cetera. An <a shape="rect" href="expression.html">Expression</a> can only be used to set the IN body. </p>
-
-<p>From <strong>Camel 2.3</strong> onwards the <a shape="rect" href="expression.html">Expression</a> or <a shape="rect" href="processor.html">Processor</a> is pre-populated with a copy of the original <a shape="rect" href="exchange.html">Exchange</a>, which allows you to access the original message when you prepare a new <a shape="rect" href="exchange.html">Exchange</a> to be sent. You can use the <code>copy</code> option (enabled by default) to indicate whether you want this.  If you set <code>copy=false</code>, then it works as in Camel 2.2 or older where the <a shape="rect" href="exchange.html">Exchange</a> will be empty.</p>
-
-<p>Below is the processor variation. This example is from Camel 2.3, where we disable <code>copy</code> by passing in <code>false</code> to create a new, empty <a shape="rect" href="exchange.html">Exchange</a>. </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="BookInOnePage-Sendinganew">Sending a new <a shape="rect" href="exchange.html">Exchange</a></h4><p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent Builders</a></strong><br clear="none"> Camel supports either a processor or an <a shape="rect" href="expression.html">Expression</a> to populate the new <a shape="rect" href="exchange.html">Exchange</a>. Using a processor gives you full power over how the <a shape="rect" href="exchange.html">Exchange</a> is populated as you can set properties, headers, et cetera. An <a shape="rect" href="expression.html">Expression</a> can only be used to set the IN body.</p><p>From <strong>Camel 2.3</strong> onwards the <a shape="rect" href="expression.html">Expression</a> or <a shape="rect" href="processor.html">Processor</a> is pre-populated with a copy of the original <a shape="rect" href="exchange.html">Exchange</a>, which allows you to access the original message when you prepare a new <a shape="rect" href="ex
 change.html">Exchange</a> to be sent. You can use the <code>copy</code> option (enabled by default) to indicate whether you want this. If you set <code>copy=false</code>, then it works as in Camel 2.2 or older where the <a shape="rect" href="exchange.html">Exchange</a> will be empty.</p><p>Below is the processor variation. This example is from Camel 2.3, where we disable <code>copy</code> by passing in <code>false</code> to create a new, empty <a shape="rect" href="exchange.html">Exchange</a>.</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(&quot;direct:start&quot;)
     .wireTap(&quot;direct:foo&quot;, false, new Processor() {
@@ -21800,10 +21760,7 @@ from(&quot;direct:start&quot;)
 
 from(&quot;direct:foo&quot;).to(&quot;mock:foo&quot;);
 ]]></script>
-</div></div>
-
-<p>Here is the <a shape="rect" href="expression.html">Expression</a> variation. This example is from Camel 2.3, where we disable <code>copy</code> by passing in <code>false</code> to create a new, empty <a shape="rect" href="exchange.html">Exchange</a>. </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Here is the <a shape="rect" href="expression.html">Expression</a> variation. This example is from Camel 2.3, where we disable <code>copy</code> by passing in <code>false</code> to create a new, empty <a shape="rect" href="exchange.html">Exchange</a>.</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(&quot;direct:start&quot;)
     .wireTap(&quot;direct:foo&quot;, false, constant(&quot;Bye World&quot;))
@@ -21811,11 +21768,7 @@ from(&quot;direct:start&quot;)
 
 from(&quot;direct:foo&quot;).to(&quot;mock:foo&quot;);
 ]]></script>
-</div></div>
-
-<p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong><br clear="none">
-The processor variation, which uses a <strong>processorRef</strong> attribute to refer to a Spring bean by ID: </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong><br clear="none"> The processor variation, which uses a <strong>processorRef</strong> attribute to refer to a Spring bean by ID:</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[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start2&quot;/&gt;
@@ -21823,10 +21776,7 @@ The processor variation, which uses a <s
     &lt;to uri=&quot;mock:result&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<p>Here is the <a shape="rect" href="expression.html">Expression</a> variation, where the expression is defined in the <strong>body</strong> tag: </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Here is the <a shape="rect" href="expression.html">Expression</a> variation, where the expression is defined in the <strong>body</strong> tag:</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[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
@@ -21836,10 +21786,7 @@ The processor variation, which uses a <s
     &lt;to uri=&quot;mock:result&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<p>This variation accesses the body of the original message and creates a new <a shape="rect" href="exchange.html">Exchange</a> based on the <a shape="rect" href="expression.html">Expression</a>.  It will create a new Exchange and have the body contain <code>"Bye ORIGINAL BODY MESSAGE HERE"</code></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>This variation accesses the body of the original message and creates a new <a shape="rect" href="exchange.html">Exchange</a> based on the <a shape="rect" href="expression.html">Expression</a>. It will create a new Exchange and have the body contain <code>"Bye ORIGINAL BODY MESSAGE HERE"</code></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[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
@@ -21849,23 +21796,7 @@ The processor variation, which uses a <s
     &lt;to uri=&quot;mock:result&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-<h4 id="BookInOnePage-FurtherExample">Further Example</h4>
-
-<p>For another example of this pattern, refer to the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/WireTapTest.java">wire tap test case</a>.</p>
-
-<h3 id="BookInOnePage-SendinganewandsetheadersinDSL">Sending a new <a shape="rect" href="exchange.html">Exchange</a> and set headers in DSL</h3>
-<p><strong>Available as of Camel 2.8</strong></p>
-
-<p>If you send a new message using <a shape="rect" href="wire-tap.html">Wire Tap</a>, then you could only set the message body using an <a shape="rect" href="expression.html">Expression</a> from the DSL. If you also need to set headers, you would have to use a <a shape="rect" href="processor.html">Processor</a>. In Camel 2.8 onwards, you can now set headers as well in the DSL.</p>
-
-<p>The following example sends a new message which has</p>
-<ul class="alternate"><li>"Bye World" as message body</li><li>a header with key "id" with the value 123</li><li>a header with key "date" which has current date as value</li></ul>
-
-
-<h4 id="BookInOnePage-JavaDSL.3">Java DSL</h4>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="BookInOnePage-FurtherExample">Further Example</h4><p>For another example of this pattern, refer to the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/WireTapTest.java">wire tap test case</a>.</p><h3 id="BookInOnePage-SendinganewandsetheadersinDSL">Sending a new <a shape="rect" href="exchange.html">Exchange</a> and set headers in DSL</h3><p><strong>Available as of Camel 2.8</strong></p><p>If you send a new message using <a shape="rect" href="wire-tap.html">Wire Tap</a>, then you could only set the message body using an <a shape="rect" href="expression.html">Expression</a> from the DSL. If you also need to set headers, you would have to use a <a shape="rect" href="processor.html">Processor</a>. In Camel 2.8 onwards, you can now set headers as well in the DSL.</p><p>The following example sends a new message which has</p><ul class="alternate"><li>"Bye World" as message body</
 li><li>a header with key "id" with the value 123</li><li>a header with key "date" which has current date as value</li></ul><h4 id="BookInOnePage-JavaDSL.3">Java DSL</h4><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(&quot;direct:start&quot;)
     // tap a new message and send it to direct:tap
@@ -21883,11 +21814,7 @@ from(&quot;direct:start&quot;)
 from(&quot;direct:tap&quot;)
     .to(&quot;mock:tap&quot;);
 ]]></script>
-</div></div>
-
-<h4 id="BookInOnePage-XMLDSL">XML DSL</h4>
-<p>The XML DSL is slightly different than Java DSL in how you configure the message body and headers using &lt;body&gt; and &lt;setHeader&gt;:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="BookInOnePage-XMLDSL">XML DSL</h4><p>The XML DSL is slightly different than Java DSL in how you configure the message body and headers using &lt;body&gt; and &lt;setHeader&gt;:</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[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
@@ -21903,16 +21830,7 @@ from(&quot;direct:tap&quot;)
     &lt;to uri=&quot;mock:result&quot;/&gt;
 &lt;/route&gt;
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-UsingonPreparetoexecutecustomlogicwhenpreparingmessages.3">Using onPrepare to execute custom logic when preparing messages</h3>
-<p><strong>Available as of Camel 2.8</strong></p>
-
-<p>See details at <a shape="rect" href="multicast.html">Multicast</a></p>
-
-
-<h4 id="BookInOnePage-UsingThisPattern.47">Using This Pattern</h4>
+</div></div><h3 id="BookInOnePage-UsingonPreparetoexecutecustomlogicwhenpreparingmessages.3">Using onPrepare to execute custom logic when preparing messages</h3><p><strong>Available as of Camel 2.8</strong></p><p>See details at <a shape="rect" href="multicast.html">Multicast</a></p><p></p><h4 id="BookInOnePage-UsingThisPattern.47">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>
 <h2 id="BookInOnePage-Log">Log</h2>
@@ -23874,11 +23792,11 @@ template.send(&quot;direct:alias-verify&
 <p>The <strong>cxf:</strong> component provides integration with <a shape="rect" href="http://cxf.apache.org">Apache CXF</a> for connecting to JAX-WS services hosted in CXF.</p>
 
 <style type="text/css">/*<![CDATA[*/
-div.rbtoc1387228664390 {padding: 0px;}
-div.rbtoc1387228664390 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1387228664390 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1387419565670 {padding: 0px;}
+div.rbtoc1387419565670 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1387419565670 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style><div class="toc-macro rbtoc1387228664390">
+/*]]>*/</style><div class="toc-macro rbtoc1387419565670">
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF Component</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-Thedescriptionsofthedataformats">The descriptions of the dataformats</a>
@@ -28981,71 +28899,33 @@ hibernate:[entityClassName][?options]
 <h3 id="BookInOnePage-SeeAlso.41">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="hibernate-example.html">Hibernate Example</a></li></ul>
-<h2 id="BookInOnePage-HL7Component">HL7 Component</h2>
-
-<p>The <strong>hl7</strong> component is used for working with the HL7 MLLP protocol and <a shape="rect" class="external-link" href="http://www.hl7.org/" rel="nofollow">HL7 v2 messages</a> using the <a shape="rect" class="external-link" href="http://hl7api.sourceforge.net" rel="nofollow">HAPI library</a>.</p>
-
-<p>This component supports the following:</p>
-<ul class="alternate"><li>HL7 MLLP codec for <a shape="rect" class="external-link" href="http://mina.apache.org/">Mina</a></li><li>Agnostic data format using either plain String objects or HAPI HL7 model objects.</li><li><a shape="rect" href="type-converter.html">Type Converter</a> from/to HAPI and String</li><li>HL7 DataFormat using HAPI library</li><li>Even more ease-of-use as it's integrated well with the <a shape="rect" href="mina.html">camel-mina</a> (<strong>Camel 2.11</strong>: <a shape="rect" href="mina2.html">camel-mina2</a> ) component.</li></ul>
-
-
-<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[
-&lt;dependency&gt;
+<h2 id="BookInOnePage-HL7Component">HL7 Component</h2><p>The <strong>hl7</strong> component is used for working with the HL7 MLLP protocol and <a shape="rect" class="external-link" href="http://www.hl7.org/" rel="nofollow">HL7 v2 messages</a> using the <a shape="rect" class="external-link" href="http://hl7api.sourceforge.net" rel="nofollow">HAPI library</a>.</p><p>This component supports the following:</p><ul class="alternate"><li>HL7 MLLP codec for <a shape="rect" class="external-link" href="http://mina.apache.org/">Mina</a></li><li>Agnostic data format using either plain String objects or HAPI HL7 model objects.</li><li><a shape="rect" href="type-converter.html">Type Converter</a> from/to HAPI and String</li><li>HL7 DataFormat using HAPI library</li><li>Even more ease-of-use as it's integrated well with the <a shape="rect" href="mina.html">camel-mina</a> (<strong>Camel 2.11</strong>: <a shape="rect" href="mina2.html">camel-mina2</a> ) component.</li></ul><p>Maven users will need t
 o 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[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-hl7&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-HL7MLLPprotocol">HL7 MLLP protocol</h3>
-<p>HL7 is often used with the HL7 MLLP protocol that is a text based TCP socket based protocol. This component ships with a Mina Codec that conforms to the MLLP protocol so you can easily expose a HL7 listener that accepts HL7 requests over the TCP transport. </p>
-
-<p>To expose a HL7 listener service we reuse the existing mina/mina2 component where we just use the <code>HL7MLLPCodec</code> as codec.</p>
-
-<p>The HL7 MLLP codec has the following options:</p>
-<div class="confluenceTableSmall">
+</div></div><h3 id="BookInOnePage-HL7MLLPprotocol">HL7 MLLP protocol</h3><p>HL7 is often used with the HL7 MLLP protocol that is a text based TCP socket based protocol. This component ships with a Mina Codec that conforms to the MLLP protocol so you can easily expose a HL7 listener that accepts HL7 requests over the TCP transport.</p><p>To expose a HL7 listener service we reuse the existing mina/mina2 component where we just use the <code>HL7MLLPCodec</code> as codec.</p><p>The HL7 MLLP codec has the following options:</p><div class="confluenceTableSmall">
 <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>startByte</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0x0b</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The start byte spanning the HL7 payload. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>endByte1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0x1c</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The first end byte spanning the HL7 payload.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>endByte2</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0x0d</code> </p></td><td colsp
 an="1" rowspan="1" class="confluenceTd"><p> The 2nd end byte spanning the HL7 payload. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>charset</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> JVM Default </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The encoding (is a <a shape="rect" class="external-link" href="http://docs.oracle.com/javase/6/docs/api/java/nio/charset/Charset.html" rel="nofollow">charset name</a>) to use for the codec. If not provided, Camel will use the <a shape="rect" class="external-link" href="http://docs.oracle.com/javase/6/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>convertLFtoCR</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> (<strong>Camel 2.11</strong>:<code>false</code>) </p></td><td colspan="1" rowspan="1" class="confluenceTd
 "><p> Will convert <code>\n</code> to <code>\r</code> (<code>0x0d</code>, 13 decimal) as HL7 stipulates <code>\r</code> as segment terminators. The HAPI library requires the use of <code>\r</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>validate</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 HAPI Parser should validate or not. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>parser</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>ca.uhn.hl7v2.parser.PipeParser</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> To use a custom parser. Must be of type <code>ca.uhn.hl7v2.parser.Parser</code>. </p></td></tr></tbody></table>
-</div>
-
-<h4 id="BookInOnePage-ExposingaHL7listener">Exposing a HL7 listener</h4>
-<p>In our Spring XML file, we configure an endpoint to listen for HL7 requests using TCP:</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[
-        &lt;endpoint id=&quot;hl7listener&quot; uri=&quot;mina:tcp://localhost:8888?sync=true&amp;amp;codec=#hl7codec&quot;/&gt;
+</div><h4 id="BookInOnePage-ExposingaHL7listener">Exposing a HL7 listener</h4><p>In our Spring XML file, we configure an endpoint to listen for HL7 requests using TCP:</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[        &lt;endpoint id=&quot;hl7listener&quot; uri=&quot;mina:tcp://localhost:8888?sync=true&amp;amp;codec=#hl7codec&quot;/&gt;
         &lt;!-- Camel 2.11: uri=&quot;mina2:tcp... --&gt;
 ]]></script>
-</div></div>
-<p>Notice that we use TCP on <code>localhost</code> on port <code>8888</code>. We use <strong>sync=true</strong> to indicate that this listener is synchronous and therefore will return a HL7 response to the caller. Then we setup mina to use our HL7 codec with <strong>codec=#hl7codec</strong>. Notice that <code>hl7codec</code> is just a Spring bean ID, so we could have named it <code>mygreatcodecforhl7</code> or whatever. The codec is also set up in the Spring XML file:</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[
-    &lt;bean id=&quot;hl7codec&quot; class=&quot;org.apache.camel.component.hl7.HL7MLLPCodec&quot;&gt;
+</div></div><p>Notice that we use TCP on <code>localhost</code> on port <code>8888</code>. We use <strong>sync=true</strong> to indicate that this listener is synchronous and therefore will return a HL7 response to the caller. Then we setup mina to use our HL7 codec with <strong>codec=#hl7codec</strong>. Notice that <code>hl7codec</code> is just a Spring bean ID, so we could have named it <code>mygreatcodecforhl7</code> or whatever. The codec is also set up in the Spring XML file:</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[    &lt;bean id=&quot;hl7codec&quot; class=&quot;org.apache.camel.component.hl7.HL7MLLPCodec&quot;&gt;
         &lt;property name=&quot;charset&quot; value=&quot;iso-8859-1&quot;/&gt;
     &lt;/bean&gt;
 ]]></script>
-</div></div>
-<p>Above we also configure the charset encoding to use (<code>iso-8859-1</code>).</p>
-
-<p>The endpoint <strong>hl7listener</strong> can then be used in a route as a consumer, as this Java DSL example illustrates:</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(&quot;hl7listener&quot;).to(&quot;patientLookupService&quot;);
+</div></div><p>Above we also configure the charset encoding to use (<code>iso-8859-1</code>).</p><p>The endpoint <strong>hl7listener</strong> can then be used in a route as a consumer, as this Java DSL example illustrates:</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(&quot;hl7listener&quot;).to(&quot;patientLookupService&quot;);
 ]]></script>
-</div></div>
-<p>This is a very simple route that will listen for HL7 and route it to a service named <strong>patientLookupService</strong> that is also a Spring bean ID we have configured in the Spring XML as:</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[
-    &lt;bean id=&quot;patientLookupService&quot; class=&quot;com.mycompany.healthcare.service.PatientLookupService&quot;/&gt;
+</div></div><p>This is a very simple route that will listen for HL7 and route it to a service named <strong>patientLookupService</strong> that is also a Spring bean ID we have configured in the Spring XML as:</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[    &lt;bean id=&quot;patientLookupService&quot; class=&quot;com.mycompany.healthcare.service.PatientLookupService&quot;/&gt;
 ]]></script>
-</div></div>
-<p>Another powerful feature of Camel is that we can have our business logic in POJO classes that is not tied to Camel as shown here:</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[
-
-import ca.uhn.hl7v2.HL7Exception;
+</div></div><p>Another powerful feature of Camel is that we can have our business logic in POJO classes that is not tied to Camel as shown here:</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[import ca.uhn.hl7v2.HL7Exception;
 import ca.uhn.hl7v2.model.Message;
 import ca.uhn.hl7v2.model.v24.segment.QRD;
 
@@ -29059,53 +28939,23 @@ public class PatientLookupService {
         return response
     }
 ]]></script>
-</div></div>
-<p>Notice that this class uses just imports from the HAPI library and <strong>not</strong> from Camel.</p>
-
-<h3 id="BookInOnePage-HL7Modelusingjava.lang.String">HL7 Model using java.lang.String</h3>
-<p>The HL7MLLP codec uses plain <code>String</code> as its data format. Camel uses its <a shape="rect" href="type-converter.html">Type Converter</a> to convert to/from strings to the HAPI HL7 model objects. However, you can use plain <code>String</code> objects if you prefer, for instance if you wish to parse the data yourself.</p>
-
-<p>See samples for such an example.</p>
-
-<h3 id="BookInOnePage-HL7v2ModelusingHAPI">HL7v2 Model using HAPI</h3>
-<p>The HL7v2 model uses Java objects from the HAPI library. Using this library, we can encode and decode from the EDI format (ER7) that is mostly used with HL7v2.<br clear="none">
-With this model you can code with Java objects instead of the EDI based HL7 format that can be hard for humans to read and understand.</p>
-
-<p>The sample below is a request to lookup a patient with the patient ID <code>0101701234</code>.</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[
-MSH|^~\\&amp;|MYSENDER|MYRECEIVER|MYAPPLICATION||200612211200||QRY^A19|1234|P|2.4
+</div></div><p>Notice that this class uses just imports from the HAPI library and <strong>not</strong> from Camel.</p><h3 id="BookInOnePage-HL7Modelusingjava.lang.String">HL7 Model using java.lang.String</h3><p>The HL7MLLP codec uses plain <code>String</code> as its data format. Camel uses its <a shape="rect" href="type-converter.html">Type Converter</a> to convert to/from strings to the HAPI HL7 model objects. However, you can use plain <code>String</code> objects if you prefer, for instance if you wish to parse the data yourself.</p><p>See samples for such an example.</p><h3 id="BookInOnePage-HL7v2ModelusingHAPI">HL7v2 Model using HAPI</h3><p>The HL7v2 model uses Java objects from the HAPI library. Using this library, we can encode and decode from the EDI format (ER7) that is mostly used with HL7v2.<br clear="none"> With this model you can code with Java objects instead of the EDI based HL7 format that can be hard for humans to read and understand.</p><p>The sample below is a requ
 est to lookup a patient with the patient ID <code>0101701234</code>.</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[MSH|^~\\&amp;|MYSENDER|MYRECEIVER|MYAPPLICATION||200612211200||QRY^A19|1234|P|2.4
 QRD|200612211200|R|I|GetPatient|||1^RD|0101701234|DEM||
 ]]></script>
-</div></div>
-
-<p>Using the HL7 model we can work with the data as a <code>ca.uhn.hl7v2.model.Message</code> object.<br clear="none">
-To retrieve the patient ID in the message above, you can do this in Java code:</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[
-Message msg = exchange.getIn().getBody(Message.class);
+</div></div><p>Using the HL7 model we can work with the data as a <code>ca.uhn.hl7v2.model.Message</code> object.<br clear="none"> To retrieve the patient ID in the message above, you can do this in Java code:</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[Message msg = exchange.getIn().getBody(Message.class);
 QRD qrd = (QRD)msg.get(&quot;QRD&quot;);
 String patientId = qrd.getWhoSubjectFilter(0).getIDNumber().getValue();
 ]]></script>
-</div></div>
-
-<p>If you know the message type in advance, you can be more type-safe:</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[
-QRY_A19 msg = exchange.getIn().getBody(QRY_A19.class);
+</div></div><p>If you know the message type in advance, you can be more type-safe:</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[QRY_A19 msg = exchange.getIn().getBody(QRY_A19.class);
 String patientId = msg.getQRD().getWhoSubjectFilter(0).getIDNumber().getValue();
 ]]></script>
-</div></div>
-
-<p>Camel has built-in type converters, so when this operation is invoked:</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[
-Message msg = exchange.getIn().getBody(Message.class);
+</div></div><p>Camel has built-in type converters, so when this operation is invoked:</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[Message msg = exchange.getIn().getBody(Message.class);
 ]]></script>
-</div></div>
-<p>Camel will convert the received HL7 data from <code>String</code> to <code>Message</code>. This is powerful when combined with the HL7 listener, then you as the end-user don't have to work with <code>byte[]</code>, <code>String</code> or any other simple object formats. You can just use the HAPI HL7v2 model objects.</p>
-
-<h3 id="BookInOnePage-HL7DataFormat.1">HL7 DataFormat</h3>
+</div></div><p>Camel will convert the received HL7 data from <code>String</code> to <code>Message</code>. This is powerful when combined with the HL7 listener, then you as the end-user don't have to work with <code>byte[]</code>, <code>String</code> or any other simple object formats. You can just use the HAPI HL7v2 model objects.</p><p></p><h3 id="BookInOnePage-HL7DataFormat.1">HL7 DataFormat</h3>
 <p>The <a shape="rect" href="hl7.html">HL7</a> component ships with a HL7 data format that can be used to format between <code>String</code> and HL7 model objects. </p>
 <ul class="alternate"><li><code>marshal</code> = from Message to byte stream (can be used when returning as response using the HL7 MLLP codec)</li><li><code>unmarshal</code> = from byte stream to Message (can be used when receiving streamed data from the HL7 MLLP</li></ul>
 
@@ -29158,38 +29008,13 @@ Then you don't need to create an instanc
                     </div>
     </div>
 
-
-
-<h3 id="BookInOnePage-MessageHeaders.5">Message Headers</h3>
-<p>The <strong>unmarshal</strong> operation adds these MSH fields as headers on the Camel message:</p>
-
-<div class="confluenceTableSmall">
+<h3 id="BookInOnePage-MessageHeaders.5">Message Headers</h3><p>The <strong>unmarshal</strong> operation adds these MSH fields as headers on the Camel message:</p><div class="confluenceTableSmall">
 <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Key </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> MSH field </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Example </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHL7SendingApplication</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MSH-3</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MYSERVER</code> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHL7SendingFacility</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MSH-4</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MYSERVERAPP</code> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHL7ReceivingApplication</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MSH-5</code> </p></td><
 td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MYCLIENT</code> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHL7ReceivingFacility</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MSH-6</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MYCLIENTAPP</code> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHL7Timestamp</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MSH-7</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>20071231235900</code> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHL7Security</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MSH-8</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHL7MessageType</code> </p></
 td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MSH-9-1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>ADT</code> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHL7TriggerEvent</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MSH-9-2</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>A01</code> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHL7MessageControl</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MSH-10</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>1234</code> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelHL7ProcessingId</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MSH-11</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>P</code> </p></td></tr><tr><td colspan="1" rowspan
 ="1" class="confluenceTd"><p> <code>CamelHL7VersionId</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>MSH-12</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>2.4</code> </p></td></tr></tbody></table>
-</div>
-
-<p>All headers are <code>String</code> types. If a header value is missing, its value is <code>null</code>.</p>
-
-<h3 id="BookInOnePage-Options.42">Options</h3>
-<p>The HL7 Data Format supports the following options:</p>
-<div class="confluenceTableSmall">
+</div><p>All headers are <code>String</code> types. If a header value is missing, its value is <code>null</code>.</p><h3 id="BookInOnePage-Options.42">Options</h3><p>The HL7 Data Format supports the following options:</p><div class="confluenceTableSmall">
 <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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>validate</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Whether the HAPI Parser should validate using the default validation rules. <strong>Camel 2.11:</strong> better use the <code>parser</code> option and initialize the parser with the desired HAPI <code>ValidationContext</code> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>parser</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>ca.uhn.hl7v2.parser.GenericParser</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> To use a cus
 tom parser. Must be of type <code>ca.uhn.hl7v2.parser.Parser</code>. Note that <code>GenericParser</code> also allows to parse XML-encoded HL7v2 messages. </p></td></tr></tbody></table>
 
-</div>
-
-<h3 id="BookInOnePage-Dependencies.37">Dependencies</h3>
-
-<p>To use HL7 in your Camel routes you'll need to add a dependency on <strong>camel-hl7</strong> listed above, which implements this data format. </p>
-
-<p>The HAPI library since Version 0.6 has been split into a <a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-base" rel="nofollow">base library</a> and several structure libraries, one for each HL7v2 message version:</p>
-
-<ul><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v21" rel="nofollow">v2.1 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v22" rel="nofollow">v2.2 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v23" rel="nofollow">v2.3 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v231" rel="nofollow">v2.3.1 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v24" rel="nofollow">v2.4 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v25" rel="nofollow">v2.5 structures library</a></li><li><a shape="rect" class="external-link" 
 href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v251" rel="nofollow">v2.5.1 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v26" rel="nofollow">v2.6 structures library</a></li></ul>
-
-
-<p>By default <code>camel-hl7</code> only references the HAPI <a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-base" rel="nofollow">base library</a>. Applications are responsible for including structure libraries themselves. For example, if a application works with HL7v2 message versions 2.4 and 2.5 then the following dependencies must be added:</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[
-&lt;dependency&gt;
+</div><h3 id="BookInOnePage-Dependencies.37">Dependencies</h3><p>To use HL7 in your Camel routes you'll need to add a dependency on <strong>camel-hl7</strong> listed above, which implements this data format.</p><p>The HAPI library since Version 0.6 has been split into a <a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-base" rel="nofollow">base library</a> and several structure libraries, one for each HL7v2 message version:</p><ul><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v21" rel="nofollow">v2.1 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v22" rel="nofollow">v2.2 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v23" rel="nofollow">v2.3 structures library</a></li><li><a shape="rect" class="external-link" href=
 "http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v231" rel="nofollow">v2.3.1 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v24" rel="nofollow">v2.4 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v25" rel="nofollow">v2.5 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v251" rel="nofollow">v2.5.1 structures library</a></li><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-structures-v26" rel="nofollow">v2.6 structures library</a></li></ul><p>By default <code>camel-hl7</code> only references the HAPI <a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-base" rel="nofollow">base library</a>. Applications are responsible for including structur
 e libraries themselves. For example, if a application works with HL7v2 message versions 2.4 and 2.5 then the following dependencies must be added:</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[&lt;dependency&gt;
     &lt;groupId&gt;ca.uhn.hapi&lt;/groupId&gt;
     &lt;artifactId&gt;hapi-structures-v24&lt;/artifactId&gt;
     &lt;version&gt;1.2&lt;/version&gt;
@@ -29202,30 +29027,15 @@ Then you don't need to create an instanc
     &lt;!-- use the same version as your hapi-base version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div>
-
-<p>Alternatively, an OSGi bundle containing the base library, all structures libraries and required dependencies (on the bundle classpath) can be downloaded from the <a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-osgi-base" rel="nofollow">central Maven repository</a>. </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[
-&lt;dependency&gt;
+</div></div><p>Alternatively, an OSGi bundle containing the base library, all structures libraries and required dependencies (on the bundle classpath) can be downloaded from the <a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/ca/uhn/hapi/hapi-osgi-base" rel="nofollow">central Maven repository</a>.</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[&lt;dependency&gt;
     &lt;groupId&gt;ca.uhn.hapi&lt;/groupId&gt;
     &lt;artifactId&gt;hapi-osgi-base&lt;/artifactId&gt;
     &lt;version&gt;1.2&lt;/version&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-Terserlanguage(Camel2.11)">Terser language (<strong>Camel 2.11</strong>)</h3>
-
-<p><a shape="rect" class="external-link" href="http://hl7api.sourceforge.net" rel="nofollow">HAPI</a> provides a <a shape="rect" class="external-link" href="http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/util/Terser.html" rel="nofollow">Terser</a> class that provides access to fields using a commonly used terse location specification syntax. The Terser language allows to use this syntax to extract values from messages and to use them as expressions and predicates for filtering, content-based routing etc.</p>
-
-<p>Sample:</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[
-import static org.apache.camel.component.hl7.HL7.terser;
+</div></div><h3 id="BookInOnePage-Terserlanguage(Camel2.11)">Terser language (<strong>Camel 2.11</strong>)</h3><p><a shape="rect" class="external-link" href="http://hl7api.sourceforge.net" rel="nofollow">HAPI</a> provides a <a shape="rect" class="external-link" href="http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/util/Terser.html" rel="nofollow">Terser</a> class that provides access to fields using a commonly used terse location specification syntax. The Terser language allows to use this syntax to extract values from messages and to use them as expressions and predicates for filtering, content-based routing etc.</p><p>Sample:</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[import static org.apache.camel.component.hl7.HL7.terser;
 ...
 
    // extract patient ID from field QRD-8 in the QRY_A19 message above and put into message header
@@ -29239,19 +29049,8 @@ import static org.apache.camel.component
       .to(&quot;mock:test2&quot;);
 
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-HL7Validationpredicate(Camel2.11)">HL7 Validation predicate (<strong>Camel 2.11</strong>)</h3>
-
-<p>Often it is preferable to parse a HL7v2 message and validate it against a HAPI <a shape="rect" class="external-link" href="http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/validation/ValidationContext.html" rel="nofollow">ValidationContext</a> in a separate step afterwards.</p>
-
-<p>Sample:</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[
-
-import static org.apache.camel.component.hl7.HL7.messageConformsTo;
+</div></div><h3 id="BookInOnePage-HL7Validationpredicate(Camel2.11)">HL7 Validation predicate (<strong>Camel 2.11</strong>)</h3><p>Often it is preferable to parse a HL7v2 message and validate it against a HAPI <a shape="rect" class="external-link" href="http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/validation/ValidationContext.html" rel="nofollow">ValidationContext</a> in a separate step afterwards.</p><p>Sample:</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[import static org.apache.camel.component.hl7.HL7.messageConformsTo;
 import ca.uhn.hl7v2.validation.impl.DefaultValidation;
 ...
 
@@ -29261,17 +29060,8 @@ import ca.uhn.hl7v2.validation.impl.Defa
    // Throws PredicateValidationException if message does not validate
    from(&quot;direct:test1&quot;).validate(messageConformsTo(defaultContext)).to(&quot;mock:test1&quot;);
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-HL7Acknowledgementexpression(Camel2.11)">HL7 Acknowledgement expression (<strong>Camel 2.11</strong>)</h3>
-
-<p>A common task in HL7v2 processing is to generate an acknowledgement message as response to an incoming HL7v2 message, e.g. based on a validation result. The <code>ack</code> expression lets us accomplish this very elegantly:</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[
-
-import static org.apache.camel.component.hl7.HL7.messageConformsTo;
+</div></div><h3 id="BookInOnePage-HL7Acknowledgementexpression(Camel2.11)">HL7 Acknowledgement expression (<strong>Camel 2.11</strong>)</h3><p>A common task in HL7v2 processing is to generate an acknowledgement message as response to an incoming HL7v2 message, e.g. based on a validation result. The <code>ack</code> expression lets us accomplish this very elegantly:</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[import static org.apache.camel.component.hl7.HL7.messageConformsTo;
 import static org.apache.camel.component.hl7.HL7.ack;
 import ca.uhn.hl7v2.validation.impl.DefaultValidation;
 ...
@@ -29290,12 +29080,7 @@ import ca.uhn.hl7v2.validation.impl.Defa
       // acknowledgement
       .transform(ack())
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-MoreSamples">More Samples</h3>
-<p>In the following example we send a HL7 request to a HL7 listener and retrieves a response. We use plain <code>String</code> types in this example:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookInOnePage-MoreSamples">More Samples</h3><p>In the following example we send a HL7 request to a HL7 listener and retrieves a response. We use plain <code>String</code> types in this example:</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 line1 = &quot;MSH|^~\\&amp;|MYSENDER|MYRECEIVER|MYAPPLICATION||200612211200||QRY^A19|1234|P|2.4&quot;;
 String line2 = &quot;QRD|200612211200|R|I|GetPatient|||1^RD|0101701234|DEM||&quot;;
@@ -29307,12 +29092,7 @@ in.append(line2);
 
 String out = (String)template.requestBody(&quot;mina2:tcp://127.0.0.1:8888?sync=true&amp;codec=#hl7codec&quot;, in.toString());
 ]]></script>
-</div></div>
-
-<p>In the next sample, we want to route HL7 requests from our HL7 listener to our business logic. We have our business logic in a plain POJO that we have registered in the registry as <code>hl7service</code> = for instance using Spring and letting the bean id = <code>hl7service</code>.</p>
-
-<p>Our business logic is a plain POJO only using the HAPI library so we have these operations defined:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>In the next sample, we want to route HL7 requests from our HL7 listener to our business logic. We have our business logic in a plain POJO that we have registered in the registry as <code>hl7service</code> = for instance using Spring and letting the bean id = <code>hl7service</code>.</p><p>Our business logic is a plain POJO only using the HAPI library so we have these operations defined:</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 class MyHL7BusinessLogic {
 
@@ -29334,10 +29114,7 @@ public class MyHL7BusinessLogic {
     }
 }
 ]]></script>
-</div></div>
-
-<p>Then we set up the Camel routes using the <code>RouteBuilder</code> as follows:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Then we set up the Camel routes using the <code>RouteBuilder</code> 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[
 DataFormat hl7 = new HL7DataFormat();
 // we setup or HL7 listener on port 8888 (using the hl7codec) and in sync mode so we can return a response
@@ -29364,14 +29141,7 @@ from(&quot;mina2:tcp://127.0.0.1:8888?sy
     // marshal response back
     .marshal(hl7);
 ]]></script>
-</div></div>
-
-<p>Notice that we use the HL7 DataFormat to enrich our Camel Message with the MSH fields preconfigured on the Camel Message. This lets us much more easily define our routes using the fluent builders.<br clear="none">
-If we do not use the HL7 DataFormat, then we do not gains these headers and we must resort to a different technique for computing the MSH trigger event (= what kind of HL7 message it is). This is a big advantage of the HL7 DataFormat over the plain HL7 type converters.</p>
-
-<h4 id="BookInOnePage-SampleusingplainStringobjects">Sample using plain String objects</h4>
-<p>In this sample we use plain <code>String</code> objects as the data format, that we send, process and receive. As the sample is part of a unit test, there is some code for assertions, but you should be able to understand what happens. First we send the plain string, <code>Hello World</code>, to the <code>HL7MLLPCodec</code> and receive the response as a plain string, <code>Bye World</code>.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Notice that we use the HL7 DataFormat to enrich our Camel Message with the MSH fields preconfigured on the Camel Message. This lets us much more easily define our routes using the fluent builders.<br clear="none"> If we do not use the HL7 DataFormat, then we do not gains these headers and we must resort to a different technique for computing the MSH trigger event (= what kind of HL7 message it is). This is a big advantage of the HL7 DataFormat over the plain HL7 type converters.</p><h4 id="BookInOnePage-SampleusingplainStringobjects">Sample using plain String objects</h4><p>In this sample we use plain <code>String</code> objects as the data format, that we send, process and receive. As the sample is part of a unit test, there is some code for assertions, but you should be able to understand what happens. First we send the plain string, <code>Hello World</code>, to the <code>HL7MLLPCodec</code> and receive the response as a plain string, <code>Bye World</code>.</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(&quot;mock:result&quot;);
 mock.expectedBodiesReceived(&quot;Bye World&quot;);
@@ -29384,10 +29154,7 @@ assertMockEndpointsSatisfied();
 // and the response is also just plain String
 assertEquals(&quot;Bye World&quot;, out);
 ]]></script>
-</div></div>
-
-<p>Here we process the incoming data as plain String and send the response also as plain String:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Here we process the incoming data as plain String and send the response also as plain String:</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(&quot;mina2:tcp://127.0.0.1:8888?sync=true&amp;codec=#hl7codec&quot;)
     .process(new Processor() {
@@ -29402,9 +29169,7 @@ from(&quot;mina2:tcp://127.0.0.1:8888?sy
     })
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-SeeAlso.42">See Also</h3>
+</div></div><p></p><h3 id="BookInOnePage-SeeAlso.42">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>
 <h2 id="BookInOnePage-HTTPComponent">HTTP Component</h2>
 
@@ -29756,9 +29521,9 @@ ProtocolSocketFactory factory =
 
 Protocol.registerProtocol(&quot;https&quot;,
         new Protocol(
-ÊÊÊÊÊÊÊ &quot;https&quot;,
-ÊÊÊÊÊÊÊ factory,
-ÊÊÊÊÊÊÊ 443));
+        &quot;https&quot;,
+        factory,
+        443));
 
 from(&quot;direct:start&quot;)
         .to(&quot;https://mail.google.com/mail/&quot;).to(&quot;mock:results&quot;);
@@ -32639,7 +32404,7 @@ public class Jt400RouteBuilder extends R
 public class Jt400RouteBuilder extends RouteBuilder {
     @Override
     public void configure() throws Exception {
-       from(&quot;direct:work&quot;).to(&quot;jt400://GRUPO:ATWORK@server/QSYS.LIB/assets.LIB/compute.PGM?fieldsLength=10,10,512&amp;ouputFieldsIdx=2,3&quot;).to(Òdirect:playÓ);
+       from(&quot;direct:work&quot;).to(&quot;jt400://GRUPO:ATWORK@server/QSYS.LIB/assets.LIB/compute.PGM?fieldsLength=10,10,512&amp;ouputFieldsIdx=2,3&quot;).to(“direct:play”);
     }
 }
 ]]></script>
@@ -38231,39 +37996,16 @@ public final class ServletActivator impl
 <h3 id="BookInOnePage-SeeAlso.77">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="servlet-tomcat-example.html">Servlet Tomcat Example</a></li><li><a shape="rect" href="servlet-tomcat-no-spring-example.html">Servlet Tomcat No Spring Example</a></li><li><a shape="rect" href="http.html">Http</a></li><li><a shape="rect" href="jetty.html">Jetty</a></li></ul>
-<h2 id="BookInOnePage-ShiroSecurityComponent">Shiro Security Component</h2>
-
-<p><strong>Available as of Camel 2.5</strong></p>
-
-<p>The <strong>shiro-security</strong> component in Camel is a security focused component, based on the Apache Shiro security project.</p>
-
-<p>Apache Shiro is a powerful and flexible open-source security framework that cleanly handles authentication, authorization, enterprise session management and cryptography. The objective of the Apache Shiro project is to provide the most robust and comprehensive application security framework available while also being very easy to understand and extremely simple to use.</p>
-
-<p>This camel shiro-security component allows authentication and authorization support to be applied to different segments of a camel route.</p>
-
-<p>Shiro security is applied on a route using a Camel Policy. A Policy in Camel utilizes a strategy pattern for applying interceptors on Camel Processors. It offering the ability to apply cross-cutting concerns (for example. security, transactions etc) on sections/segments of a camel route. </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="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;dependency&gt;
+<h2 id="BookInOnePage-ShiroSecurityComponent">Shiro Security Component</h2><p><strong>Available as of Camel 2.5</strong></p><p>The <strong>shiro-security</strong> component in Camel is a security focused component, based on the Apache Shiro security project.</p><p>Apache Shiro is a powerful and flexible open-source security framework that cleanly handles authentication, authorization, enterprise session management and cryptography. The objective of the Apache Shiro project is to provide the most robust and comprehensive application security framework available while also being very easy to understand and extremely simple to use.</p><p>This camel shiro-security component allows authentication and authorization support to be applied to different segments of a camel route.</p><p>Shiro security is applied on a route using a Camel Policy. A Policy in Camel utilizes a strategy pattern for applying interceptors on Camel Processors. It offering the ability to apply cross-cutting concerns (f
 or example. security, transactions etc) on sections/segments of a camel route.</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="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-shiro&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-ShiroSecurityBasics">Shiro Security Basics</h3>
-
-<p>To employ Shiro security on a camel route, a ShiroSecurityPolicy object must be instantiated with security configuration details (including users, passwords, roles etc). This object must then be applied to a camel route. This ShiroSecurityPolicy Object may also be registered in the Camel registry (JNDI or ApplicationContextRegistry) and then utilized on other routes in the Camel Context.</p>
-
-<p>Configuration details are provided to the ShiroSecurityPolicy using an Ini file (properties file) or an Ini object. The Ini file is a standard Shiro configuration file containing user/role details as shown below</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[
-[users]
+</div></div><h3 id="BookInOnePage-ShiroSecurityBasics">Shiro Security Basics</h3><p>To employ Shiro security on a camel route, a ShiroSecurityPolicy object must be instantiated with security configuration details (including users, passwords, roles etc). This object must then be applied to a camel route. This ShiroSecurityPolicy Object may also be registered in the Camel registry (JNDI or ApplicationContextRegistry) and then utilized on other routes in the Camel Context.</p><p>Configuration details are provided to the ShiroSecurityPolicy using an Ini file (properties file) or an Ini object. The Ini file is a standard Shiro configuration file containing user/role details as shown below</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[[users]
 # user &#39;ringo&#39; with password &#39;starr&#39; and the &#39;sec-level1&#39; role
 ringo = starr, sec-level1
 george = harrison, sec-level2
@@ -38283,15 +38025,8 @@ sec-level2 = zone1:*
 # readonly   
 sec-level1 = zone1:readonly:*
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-InstantiatingaShiroSecurityPolicyObject">Instantiating a ShiroSecurityPolicy Object</h3>
-
-<p>A ShiroSecurityPolicy object is instantiated 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[
-        private final String iniResourcePath = &quot;classpath:shiro.ini&quot;;
+</div></div><h3 id="BookInOnePage-InstantiatingaShiroSecurityPolicyObject">Instantiating a ShiroSecurityPolicy Object</h3><p>A ShiroSecurityPolicy object is instantiated 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[        private final String iniResourcePath = &quot;classpath:shiro.ini&quot;;
         private final byte[] passPhrase = {
             (byte) 0x08, (byte) 0x09, (byte) 0x0A, (byte) 0x0B,
             (byte) 0x0C, (byte) 0x0D, (byte) 0x0E, (byte) 0x0F,
@@ -38304,20 +38039,10 @@ sec-level1 = zone1:readonly:*
         final ShiroSecurityPolicy securityPolicy = 
             new ShiroSecurityPolicy(iniResourcePath, passPhrase, true, permissionsList);
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-ShiroSecurityPolicyOptions">ShiroSecurityPolicy Options</h3>
-<div class="confluenceTableSmall">
+</div></div><h3 id="BookInOnePage-ShiroSecurityPolicyOptions">ShiroSecurityPolicy Options</h3><div class="confluenceTableSmall">
 <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>iniResourcePath or ini</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>none</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Resource String or Ini Object </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A mandatory Resource String for the iniResourcePath or an instance of an Ini object must be passed to the security policy. Resources can be acquired from the file system, classpath, or URLs when prefixed with "file:, classpath:, or url:" respectively. For e.g "classpath:shiro.ini" </p></td></tr><tr><td colspan="1" rowspan="1" class="conf
 luenceTd"><p> <code>passPhrase</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>An AES 128 based key</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> byte[] </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A passPhrase to decrypt ShiroSecurityToken(s) sent along with Message Exchanges </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>alwaysReauthenticate</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> boolean </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Setting to ensure re-authentication on every individual request. If set to false, the user is authenticated and locked such than only requests from the same user going forward are authenticated. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>permissionsList</code> </p></td><td colspan="1" rowspan="1" cla
 ss="confluenceTd"><p> <code>none</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> List&lt;Permission&gt; </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A List of permissions required in order for an authenticated user to be authorized to perform further action i.e continue further on the route. If no Permissions list is provided to the ShiroSecurityPolicy object, then authorization is deemed as not required </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>cipherService</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>AES</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> org.apache.shiro.crypto.CipherService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Shiro ships with AES &amp; Blowfish based CipherServices. You may use one these or pass in your own Cipher implementation </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>base64</code>
  </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12:</strong> To use base64 encoding for the security token header, which allows transferring the header over <a shape="rect" href="jms.html" title="JMS">JMS</a> etc. This option must also be set on <code>ShiroSecurityTokenInjector</code> as well. </p></td></tr></tbody></table>
-</div>
-
-<h3 id="BookInOnePage-ApplyingShiroAuthenticationonaCamelRoute">Applying Shiro Authentication on a Camel Route</h3>
-
-<p>The ShiroSecurityPolicy, tests and permits incoming message exchanges containing a encrypted SecurityToken in the Message Header to proceed further following proper authentication. The SecurityToken object contains a Username/Password details that are used to determine where the user is a valid user. </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[
-    protected RouteBuilder createRouteBuilder() throws Exception {
+</div><h3 id="BookInOnePage-ApplyingShiroAuthenticationonaCamelRoute">Applying Shiro Authentication on a Camel Route</h3><p>The ShiroSecurityPolicy, tests and permits incoming message exchanges containing a encrypted SecurityToken in the Message Header to proceed further following proper authentication. The SecurityToken object contains a Username/Password details that are used to determine where the user is a valid user.</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[    protected RouteBuilder createRouteBuilder() throws Exception {
         final ShiroSecurityPolicy securityPolicy = 
             new ShiroSecurityPolicy(&quot;classpath:shiro.ini&quot;, passPhrase);
         
@@ -38340,15 +38065,8 @@ sec-level1 = zone1:readonly:*
         };
     }
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-ApplyingShiroAuthorizationonaCamelRoute">Applying Shiro Authorization on a Camel Route</h3>
-
-<p>Authorization can be applied on a camel route by associating a Permissions List with the ShiroSecurityPolicy. The Permissions List specifies the permissions necessary for the user to proceed with the execution of the route segment. If the user does not have the proper permission set, the request is not authorized to continue any further.</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[
-    protected RouteBuilder createRouteBuilder() throws Exception {
+</div></div><h3 id="BookInOnePage-ApplyingShiroAuthorizationonaCamelRoute">Applying Shiro Authorization on a Camel Route</h3><p>Authorization can be applied on a camel route by associating a Permissions List with the ShiroSecurityPolicy. The Permissions List specifies the permissions necessary for the user to proceed with the execution of the route segment. If the user does not have the proper permission set, the request is not authorized to continue any further.</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[    protected RouteBuilder createRouteBuilder() throws Exception {
         final ShiroSecurityPolicy securityPolicy = 
             new ShiroSecurityPolicy(&quot;./src/test/resources/securityconfig.ini&quot;, passPhrase);
         
@@ -38371,15 +38089,8 @@ sec-level1 = zone1:readonly:*
         };
     }
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-CreatingaShiroSecurityTokenandinjectingitintoaMessageExchange">Creating a ShiroSecurityToken and injecting it into a Message Exchange</h3>
-
-<p>A ShiroSecurityToken object may be created and injected into a Message Exchange using a Shiro Processor called ShiroSecurityTokenInjector. An example of injecting a ShiroSecurityToken using a ShiroSecurityTokenInjector in the client is shown below</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[
-    ShiroSecurityToken shiroSecurityToken = new ShiroSecurityToken(&quot;ringo&quot;, &quot;starr&quot;);
+</div></div><h3 id="BookInOnePage-CreatingaShiroSecurityTokenandinjectingitintoaMessageExchange">Creating a ShiroSecurityToken and injecting it into a Message Exchange</h3><p>A ShiroSecurityToken object may be created and injected into a Message Exchange using a Shiro Processor called ShiroSecurityTokenInjector. An example of injecting a ShiroSecurityToken using a ShiroSecurityTokenInjector in the client is shown below</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[    ShiroSecurityToken shiroSecurityToken = new ShiroSecurityToken(&quot;ringo&quot;, &quot;starr&quot;);
     ShiroSecurityTokenInjector shiroSecurityTokenInjector = 

[... 60 lines stripped ...]


Mime
View raw message