camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r890761 [1/2] - in /websites/production/camel/content: cache/main.pageCache camel-2130-release.html hl7.html shiro-security.html
Date Tue, 17 Dec 2013 20:19:29 GMT
Author: buildbot
Date: Tue Dec 17 20:19:28 2013
New Revision: 890761

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-2130-release.html
    websites/production/camel/content/hl7.html
    websites/production/camel/content/shiro-security.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/camel-2130-release.html
==============================================================================
--- websites/production/camel/content/camel-2130-release.html (original)
+++ websites/production/camel/content/camel-2130-release.html Tue Dec 17 20:19:28 2013
@@ -86,7 +86,7 @@
         <tr>
         <td valign="top" width="100%">
 <div class="wiki-content maincontent"><h1 id="Camel2.13.0Release-Camel2.13.0release(currentlyinprogress)">Camel 2.13.0 release (currently in progress)</h1><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="image-wrap" style=""><img src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png" style="border: 0px solid black"></span></p></div><div style="min-height:200px"></div><h2 id="Camel2.13.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to the 2.13.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)</p><ul><li>The MBean names registered by <a shape="rect" href="camel-jmx.html">Camel JMX</a> no longer include the hostname in the <code>context</code> part, eg before <code>context=myHost/myCamelId</code> and now after <code>context=myCamelId</code>. Having the hostname in the MBean name does not bring much value, and in fact makes things more complicated as the mbean name changes depending on the host running Camel.</li><li><a shape="rect" href="camel-jmx.html">MBean naming</a> in OSGi cleaned up to use simpler naming with symbolicName. Before we could have MBean names with duplicate bundle ids such as
  <code>context=114-114-camel-6</code>, which now is using the symbolic name instead, <code>context=MyApplication</code>.</li><li>When using multiple OSGi Blueprint &lt;cm:property-placeholder&gt;'s then Camel now favors using non-default placeholders, or the last property-placeholder defined in the Blueprint XML file. This allows for example to define default properties in one placeholder, and override these values in other placeholders.</li><li><a shape="rect" href="ftp2.html">FTP</a> consumer allow to download a single named file without using the FTP LIST command. This allows to download a known file from a FTP server even when the user account does not have permission to do FTP LIST command.</li><li><a shape="rect" href="ftp2.html">FTP</a> consumer allow to ignore file not found or insufficient file permission errors.</li><li><a shape="rect" href="data-format.html">Data Format</a> using marshal now leverages <a shape="rect" href="stream-caching.html">Stream caching</a> out of th
 e box if enabled, which allows to marshal big streams and spool to disk, instead of being pure in-memory based.</li><li>Improved using <a shape="rect" href="bean.html">Bean</a> when the bean is looked up in the <a shape="rect" href="registry.html">Registry</a>, when using concurrent processing in the route.</li><li>Added <code>cache</code> option to <code>beanRef</code> and <code>&lt;bean&gt;</code> in the DSL. This avoids looking up the <a shape="rect" href="bean.html">Bean</a> from the <a shape="rect" href="registry.html">Registry</a> on each usage; this can safely be done for singleton beans.</li><li>Configuring <a shape="rect" href="data-format.html">Data Format</a>s in XML attributes now supports reference lookup using the # syntax, eg <code>&lt;jaxb xmlStreamWriterWrapper="#myWriterWrapper" ..&gt;</code></li><li><a shape="rect" href="jdbc.html">JDBC</a> component now also support <code>outputType</code> to specify the expected output as either a List or single Object. As well 
 allow to map to a bean using a <code>BeanRowMapper</code> to control the mapping of ROW names to bean properties.</li><li>Both <a shape="rect" href="quartz.html">Quartz</a> as well as <a shape="rect" href="quartz2.html">Quartz2</a> based <a shape="rect" href="scheduledroutepolicy.html">ScheduledRoutePolicy</a> has been improved to better support cluster setups (e.g. to not schedule jobs being already scheduled through another node inside a given cluster).</li><li>Reduced the work the <a shape="rect" href="aggregator2.html">Aggregate</a> EIP does while holding a lock during aggregation, which can lead to improved performance in some use-cases.</li><li><code>JndiRegistry</code> now implements all the find methods.</li><li><a shape="rect" href="vm.html">VM</a> component now supports <code>multipleConsumers=true</code> across deployment units.</li><li>Added <code>@PreConsumed</code> to <a shape="rect" href="jpa.html">JPA</a> consumer.</li><li>Added CamelFileName header support to the <a
  shape="rect" href="hdfs.html">HDFS</a> producer</li><li>Like as <code>JpaConsumer</code> now also <code>JpaProducer</code> of the <a shape="rect" href="jpa.html">JPA</a> component supports the <code>CamelEntityManager</code> header.</li><li><a shape="rect" href="restlet.html">Restlet</a> consumer now supports returning custom headers as HTTP headers from the Camel <a shape="rect" href="message.html">Message</a>.</li><li><a shape="rect" href="spring-java-config.html">Spring Java Config</a> <code>CamelConfiguration</code> now automagically detects all <code>RouteBuilder</code> instances registered in the Spring context if <code>CamelConfiguration#routes</code> method is not overridden.</li><li>Added support for transferring custom headers with <a shape="rect" href="rabbitmq.html">RabbitMQ</a> component.</li><li><a shape="rect" href="crypto.html">PGPDataFormat</a> enables stream cache during unmarshaling.</li><li><code>FileIdempotentRepository</code> now creates necessary parent direc
 tories together with the new repository file.</li><li><a shape="rect" href="properties.html">Properties</a> component and <a shape="rect" href="using-propertyplaceholder.html">property placeholder</a> will now ignore non existing JVM and environment options as well if <code>ignoreMissingLocation</code> is set to <code>true</code>.</li><li>Improved <a shape="rect" href="stream.html">Stream</a> consumer to enrich the <a shape="rect" href="message.html">Message</a> with headers about current index / completion flag.</li><li>Added <a shape="rect" href="bean-injection.html"><code>@BeanInject</code></a> to inject beans (obtained from the <a shape="rect" href="registry.html">Registry</a>) in your beans such as <code>RouteBuilder</code> classes.</li><li>Polished the <a shape="rect" href="karaf.html">Karaf</a> commands to output tables sorted and auto calculated width, so the data is formatted nicely.</li><li>Introduced <code>UnitOfWorkFactory</code> to allow end users to use custom <code>Un
 itOfWork</code> implementations created by the factory.</li><li>Doing request/reply over <a shape="rect" href="jms.html">JMS</a> allows per individual message <code>requestTimeout</code> value by specifying the timeout value in the <code>"CamelJmsRequestTimeout"</code> header.</li><li><a shape="rect" href="quartz.html">Quartz</a> and <a shape="rect" href="quartz2.html">Quartz2</a> components now enlist the quartz scheduler by default in JMX, unless configured to be disabled.</li><li><span><a shape="rect" href="twitter.html">Twitter</a> Component supports to set proxy.</span></li></ul><h3 id="Camel2.13.0Release-FixedIssues">Fixed Issues</h3><ul><li>Fixed an <code>ArrayIndexOutOfBoundsException</code> with <a shape="rect" href="message-history.html">Message History</a> when using <a shape="rect" href="seda.html">SEDA</a></li><li>Fixed <code>requestTimeout</code> on <a shape="rect" href="netty.html">Netty</a> not triggering when we have received message.</li><li>Fixed <a shape="rect" h
 ref="parameter-binding-annotations.html">Parameter Binding Annotations</a> on boolean types to evaluate as <a shape="rect" href="predicate.html">Predicate</a> instead of <a shape="rect" href="expression.html">Expression</a></li><li>Fixed using <a shape="rect" href="file2.html">File</a> consumer with <code>delete=true&amp;readLock=fileLock</code> not being able to delete the file on Windows.</li><li>Fixed <a shape="rect" href="throttler.html">Throttler</a> to honor time slots after period expires (eg so it works consistently and as expected).</li><li>Fixed getting JMSXUserID property when consuming from <a shape="rect" href="activemq.html">ActiveMQ</a></li><li>Fixed <a shape="rect" href="intercept.html">interceptFrom</a> to support property placeholders</li><li>Fixed a race condition in initializing <code>SSLContext</code> in <a shape="rect" href="netty.html">Netty</a> and <a shape="rect" href="netty-http.html">Netty HTTP</a></li><li>Fixed using <a shape="rect" href="recipient-list.h
 tml">Recipient List</a>, <a shape="rect" href="routing-slip.html">Routing Slip</a> calling another route which is configured with <code>NoErrorHandler</code>, and an exception occurred in that route, would be propagated back as not-exhausted, allow the caller route to have its error handler react on the exception.</li><li>Fixed <a shape="rect" href="quartz.html">Quartz</a> and exception was thrown when scheduling a job, would affect during shutdown, assuming the job was still in progress, and not shutdown the Quartz scheduler.</li><li>Fixed so you can configure <a shape="rect" href="stomp.html">Stomp</a> endpoints using <a shape="rect" href="uris.html">URIs</a></li><li>Fixed memory leak when using <a shape="rect" href="language.html">Language</a> component with <code>camel-script</code> languages and having <code>contentCache=false</code></li><li>Fixed <a shape="rect" href="error-handler.html">Error Handler</a> may log at <code>WARN</code> level "Cannot determine current route from 
 Exchange" when using <a shape="rect" href="splitter.html">Splitter</a></li><li>Fixed <code>camel-fop</code> to work in Apache <a shape="rect" href="karaf.html">Karaf</a> and ServiceMix</li><li>Fixed <a shape="rect" href="hdfs.html">HDFS</a> producer to use the configured <a shape="rect" href="uuidgenerator.html">UuidGenerator</a> when generating split file names to avoid filename collisions</li><li>Fixed <code>JpaProducer</code> and <code>JpaConsumer</code> of the <a shape="rect" href="jpa.html">JPA</a> component to not share/reuse the same <code>EntityManager</code> object which could cause problems if this would occur in the context of multiple/different threads.</li><li>Fixed <a shape="rect" href="http4.html">HTTP4</a> to support multiple custom component names in use, each configured using different <code>SSLContext</code>.</li><li>Fixed <a shape="rect" href="content-based-router.html">Content Based Router</a> using method call's as <a shape="rect" href="predicate.html">Predicat
 e</a>s if threw an exception, the <a shape="rect" href="content-based-router.html">Content Based Router</a> will call next predicate before triggering <a shape="rect" href="error-handler.html">Error Handler</a>.</li><li>Fixed <a shape="rect" href="netty-http.html">Netty HTTP</a> producer with query parameters may use wrong parameters from a previous call.</li><li>Fixed <a shape="rect" href="netty.html">Netty</a> producer may cause <code>NullPointerException</code> in <code>messageReceived</code> in client handler, if a <code>Channel</code> was destroyed from the producer pool.</li><li>Fixed <a shape="rect" href="file2.html">File</a> and <a shape="rect" href="ftp2.html">FTP</a> consumer(s) when <code>idempotent=true</code> could not detect changed file(s) as a new file, but would regard the file as idempotent.</li><li>Fixed <a shape="rect" href="stream.html">Stream</a> consumer reading a file using <code>groupLines</code> would not read last group of message if there was not enough l
 ines to hit the threshold.</li><li>Fixed deleting the <em>done file</em> if <a shape="rect" href="file2.html">File</a> or <a shape="rect" href="ftp2.html">FTP</a> consumer rollback and the <code>moveFailed</code> option is in use.</li><li>Fixed <a shape="rect" href="avro.html">avro</a> data format in OSGi not being able to load schema classes.</li><li>Fixed <a shape="rect" href="camel-jmx.html">JMX</a> when using custom beans in routes with <code>@ManagedResource</code> to expose JMX attributes/operations to not include Camel standard attributes/operations from its processors, which would be shown as unavailable in JMX consoles.</li><li>Fixed <a shape="rect" href="quartz2.html">Quartz2</a> simple trigger repeat count default value not working causing the trigger to only fire once, instead of forever.</li></ul><h3 id="Camel2.13.0Release-New">New <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a></h3><h3 id="Camel2.13.0Release-New.1">New <a
  shape="rect" href="components.html">Components</a></h3><ul><li><a shape="rect" href="infinispan.html"><code>camel-infinispan</code></a> - to interact with <a shape="rect" class="external-link" href="http://www.infinispan.org/" rel="nofollow">Infinispan</a> distributed data grid / cache.</li><li><a shape="rect" href="optaplanner.html"><code>camel-optaplanner</code></a> - to use <a shape="rect" class="external-link" href="http://www.optaplanner.org/" rel="nofollow">OptaPlanner</a> for problem solving plans.</li><li><a shape="rect" href="splunk.html"><code>camel-splunk</code></a> - enables you to publish and search for events in Splunk</li></ul><h3 id="Camel2.13.0Release-New.2">New <a shape="rect" href="camel-maven-archetypes.html">Camel Maven Archetypes</a></h3><ul><li>camel-archetype-cxf-code-first-blueprint</li><li>camel-archetype-cxf-contract-first-blueprint</li></ul><h3 id="Camel2.13.0Release-NewDSL">New DSL</h3><h3 id="Camel2.13.0Release-NewAnnotations">New Annotations</h3><ul><
 li><a shape="rect" href="bean-injection.html"><code>@BeanInject</code></a></li></ul><h3 id="Camel2.13.0Release-NewDataFormats">New <a shape="rect" href="data-format.html">Data Formats</a></h3><h3 id="Camel2.13.0Release-New.3">New <a shape="rect" href="languages.html">Languages</a></h3><ul><li><a shape="rect" href="jsonpath.html">JSonPath</a> - To perform <a shape="rect" href="expression.html">Expression</a> and <a shape="rect" href="predicate.html">Predicate</a> on json payloads.</li></ul><h3 id="Camel2.13.0Release-New.4">New <a shape="rect" href="examples.html">Examples</a></h3><h3 id="Camel2.13.0Release-New.5">New <a shape="rect" href="tutorials.html">Tutorials</a></h3><h3 id="Camel2.13.0Release-NewTooling">New Tooling</h3><h2 id="Camel2.13.0Release-APIchanges">API changes</h2><h2 id="Camel2.13.0Release-KnownIssues">Known Issues</h2><h2 id="Camel2.13.0Release-DependencyUpgrades">Dependency Upgrades</h2><p>You can see any dependency changes using <a shape="rect" class="external-lin
 k" href="http://vdiff.notsoclever.cc/" rel="nofollow">Camel Dependencies Version Differences web tool</a> created by Tracy Snell from the Camel <a shape="rect" href="team.html">Team</a>.</p><p>The below list is a best effort, and we may miss some updates, its better to use the <a shape="rect" class="external-link" href="http://vdiff.notsoclever.cc/" rel="nofollow">Camel Dependencies Version Differences web tool</a> which uses the released projects for comparison.</p><ul><li>AHC 1.7.20 to 1.7.21</li><li>APNS 0.1.6 to 0.2.3</li><li>AWS-SDK 1.5.1 to 1.6.3</li><li>Avro 1.7.3 to 1.7.5</li><li>BeanIO 2.0.6 to 2.0.7</li><li>CXF 2.7.6 to 2.7.8</li><li>EHCache 2.7.2 to 2.7.4</li><li>Elasticsearch 0.20.6 to 0.90.5</li><li>FOP 1.0 to 1.1</li><li>Guave 14.0.1 to 15.0</li><li>Hazelcast 2.6 to 3.0.2</li><li>ICal4j 1.0.4 to 1.0.5.2</li><li>Jclouds 1.6.2-incubating to 1.6.3</li><li>Jetty 7.6.9 to 8.1.12</li><li>Joda time 2.1 to 2.3</li><li>JRuby 1.7.4 to 1.7.5</li><li>Lucene 3.6.0 to 4.5.1</li><li>
 MongoDB Java Driver 2.11.2 to 2.11.3</li><li>Quartz 2.2.0 to 2.2.1</li><li>Restlet 2.0.15 to 2.1.4</li><li>Saxon 9.5.0.2 to 9.5.1-2</li><li>Scala 2.10.2 to 2.10.3</li><li>Servlet API 2.5 to 3.0</li><li>SolrJ 3.6.2 to 4.5.1</li><li>Spring Batch 2.2.1.RELEASE to 2.2.2.RELEASE</li><li>Spring Redis 1.0.4.RELEASE to 1.1.0.RELEASE</li><li>SSHD 0.8.0 to 0.9.0</li><li>TestNG 6.8.5 to 6.8.7</li></ul><h2 id="Camel2.13.0Release-Internalchanges">Internal changes</h2><ul><li>Add <code>RouteAware</code> API to inject <code>Route</code> for <code>Service</code>'s in routes, for example the <code>Consumer</code>'s of the routes.</li><li><code>IOHelper.gerCharsetName</code> will now lookup key <code>Exchange.CHARSET_NAME</code> in header first and then fallback to property.</li></ul><h2 id="Camel2.13.0Release-Changesthatmayaffectendusers">Changes that may affect end users</h2><ul><li>Components depending on Servlet API has been upgrade from Servlet API 2.5 to 3.0</li><li>Jetty upgraded from 7.6.x to
  8.1.x</li><li><a shape="rect" href="hazelcast-component.html">Hazelcast Component</a> uses <code>Object</code> instead of <code>String</code> as the key.</li><li><a shape="rect" href="hazelcast-component.html">Hazelcast Component</a> atomic number producer was using incorrect name (<a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-6833">CAMEL-6833</a>). Name will be different with this release.</li><li><a shape="rect" href="hazelcast-component.html">Hazelcast Component</a> instance consumer was incorrectly writing headers to the "out" message as opposed to the "in" message. Headers are now written to the "in" message.</li><li><a shape="rect" href="hazelcast-component.html">Hazelcast Component</a> map/multimap consumer were sending header value "envict" when an item was evicted. This has been corrected and the value "evicted" is used now.</li><li>The enum value <code>NON_BLOCKING</code> has been removed in <code>camel-apns</code> as its no longe
 r support in APNS itself.</li><li><code>DefaultTimeoutMap</code> must call <code>start</code> to initialize the map before use.</li><li><code>@ExcludeRoutes</code> test annotation now accepts only classes implementing <code>RoutesBuilder</code> interface.</li><li>The MBean names registered by <a shape="rect" href="camel-jmx.html">Camel JMX</a> no longer include the hostname in the <code>context</code> part, eg before <code>context=myHost/myCamelId</code> and now after <code>context=myCamelId</code>. Having the hostname in the MBean name does not bring much value, and in fact makes things more complicated as the mbean name changes depending on the host running Camel. There is an option <code>includeHostName</code> that can be configure as <code>true</code> to preserve the old behavior.</li><li><a shape="rect" href="camel-jmx.html">MBean naming</a> in OSGi cleaned up to use simpler naming with symbolicName. Before we could have MBean names with duplicate bundle ids such as <code>conte
 xt=114-114-camel-6</code>, which now is using the symbolic name instead, <code>context=MyApplication</code>.</li><li>Added <code>beforeAddRoutes</code> and <code>afterAddRoutes</code> to <code>org.apache.camel.component.servletlistener.CamelContextLifecycle</code> in <a shape="rect" href="servletlistener-component.html">ServletListener Component</a></li><li>The <a shape="rect" href="language.html">Language</a> component now no longer caches the compiled script as that could cause side-effects. You can set <code>cacheScript=true</code> to enable the previous behavior if your script is safe to do so.</li><li>The default value of <code>urlDecodeHeaders</code> option on <a shape="rect" href="netty-http.html">Netty HTTP</a> has been changed from <code>true</code> to <code>false</code>.</li></ul><h2 id="Camel2.13.0Release-Importantchangestoconsiderwhenupgrading">Important changes to consider when upgrading</h2><ul><li>If using <code>groupedExchanges</code> option on <a shape="rect" href="
 aggregator2.html">Aggregate</a> EIP then the <a shape="rect" href="exchange.html">Exchange</a>s is now stored on the message body as well. The old way of storing as a property is considered deprecated. See more details at <a shape="rect" href="aggregator2.html">Aggregate</a>.</li></ul><h2 id="Camel2.13.0Release-GettingtheDistributions">Getting the Distributions</h2><h3 id="Camel2.13.0Release-BinaryDistributions">Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.13.0/apac
 he-camel-2.13.0.zip">apache-camel-2.13.0.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/camel/apache-camel/2.13.0/apache-camel-2.13.0.zip.asc">apache-camel-2.13.0.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.13.0/apache-camel-2.13.0.tar.gz">apache-camel-2.13.0.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/camel/apache-camel/2.13.0/apache-camel-2.13.0.tar.gz.asc">apache-camel-2.13.0.tar.gz.asc</a></p></td></tr></tbody></table></div>    <div class="aui-message hint shadowed information-macro">
+<p><span class="image-wrap" style=""><img src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png" style="border: 0px solid black"></span></p></div><div style="min-height:200px"></div><h2 id="Camel2.13.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to the 2.13.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)</p><ul><li>The MBean names registered by <a shape="rect" href="camel-jmx.html">Camel JMX</a> no longer include the hostname in the <code>context</code> part, eg before <code>context=myHost/myCamelId</code> and now after <code>context=myCamelId</code>. Having the hostname in the MBean name does not bring much value, and in fact makes things more complicated as the mbean name changes depending on the host running Camel.</li><li><a shape="rect" href="camel-jmx.html">MBean naming</a> in OSGi cleaned up to use simpler naming with symbolicName. Before we could have MBean names with duplicate bundle ids such as
  <code>context=114-114-camel-6</code>, which now is using the symbolic name instead, <code>context=MyApplication</code>.</li><li>When using multiple OSGi Blueprint &lt;cm:property-placeholder&gt;'s then Camel now favors using non-default placeholders, or the last property-placeholder defined in the Blueprint XML file. This allows for example to define default properties in one placeholder, and override these values in other placeholders.</li><li><a shape="rect" href="ftp2.html">FTP</a> consumer allow to download a single named file without using the FTP LIST command. This allows to download a known file from a FTP server even when the user account does not have permission to do FTP LIST command.</li><li><a shape="rect" href="ftp2.html">FTP</a> consumer allow to ignore file not found or insufficient file permission errors.</li><li><a shape="rect" href="data-format.html">Data Format</a> using marshal now leverages <a shape="rect" href="stream-caching.html">Stream caching</a> out of th
 e box if enabled, which allows to marshal big streams and spool to disk, instead of being pure in-memory based.</li><li>Improved using <a shape="rect" href="bean.html">Bean</a> when the bean is looked up in the <a shape="rect" href="registry.html">Registry</a>, when using concurrent processing in the route.</li><li>Added <code>cache</code> option to <code>beanRef</code> and <code>&lt;bean&gt;</code> in the DSL. This avoids looking up the <a shape="rect" href="bean.html">Bean</a> from the <a shape="rect" href="registry.html">Registry</a> on each usage; this can safely be done for singleton beans.</li><li>Configuring <a shape="rect" href="data-format.html">Data Format</a>s in XML attributes now supports reference lookup using the # syntax, eg <code>&lt;jaxb xmlStreamWriterWrapper="#myWriterWrapper" ..&gt;</code></li><li><a shape="rect" href="jdbc.html">JDBC</a> component now also support <code>outputType</code> to specify the expected output as either a List or single Object. As well 
 allow to map to a bean using a <code>BeanRowMapper</code> to control the mapping of ROW names to bean properties.</li><li>Both <a shape="rect" href="quartz.html">Quartz</a> as well as <a shape="rect" href="quartz2.html">Quartz2</a> based <a shape="rect" href="scheduledroutepolicy.html">ScheduledRoutePolicy</a> has been improved to better support cluster setups (e.g. to not schedule jobs being already scheduled through another node inside a given cluster).</li><li>Reduced the work the <a shape="rect" href="aggregator2.html">Aggregate</a> EIP does while holding a lock during aggregation, which can lead to improved performance in some use-cases.</li><li><code>JndiRegistry</code> now implements all the find methods.</li><li><a shape="rect" href="vm.html">VM</a> component now supports <code>multipleConsumers=true</code> across deployment units.</li><li>Added <code>@PreConsumed</code> to <a shape="rect" href="jpa.html">JPA</a> consumer.</li><li>Added CamelFileName header support to the <a
  shape="rect" href="hdfs.html">HDFS</a> producer</li><li>Like as <code>JpaConsumer</code> now also <code>JpaProducer</code> of the <a shape="rect" href="jpa.html">JPA</a> component supports the <code>CamelEntityManager</code> header.</li><li><a shape="rect" href="restlet.html">Restlet</a> consumer now supports returning custom headers as HTTP headers from the Camel <a shape="rect" href="message.html">Message</a>.</li><li><a shape="rect" href="spring-java-config.html">Spring Java Config</a> <code>CamelConfiguration</code> now automagically detects all <code>RouteBuilder</code> instances registered in the Spring context if <code>CamelConfiguration#routes</code> method is not overridden.</li><li>Added support for transferring custom headers with <a shape="rect" href="rabbitmq.html">RabbitMQ</a> component.</li><li><a shape="rect" href="crypto.html">PGPDataFormat</a> enables stream cache during unmarshaling.</li><li><code>FileIdempotentRepository</code> now creates necessary parent direc
 tories together with the new repository file.</li><li><a shape="rect" href="properties.html">Properties</a> component and <a shape="rect" href="using-propertyplaceholder.html">property placeholder</a> will now ignore non existing JVM and environment options as well if <code>ignoreMissingLocation</code> is set to <code>true</code>.</li><li>Improved <a shape="rect" href="stream.html">Stream</a> consumer to enrich the <a shape="rect" href="message.html">Message</a> with headers about current index / completion flag.</li><li>Added <a shape="rect" href="bean-injection.html"><code>@BeanInject</code></a> to inject beans (obtained from the <a shape="rect" href="registry.html">Registry</a>) in your beans such as <code>RouteBuilder</code> classes.</li><li>Polished the <a shape="rect" href="karaf.html">Karaf</a> commands to output tables sorted and auto calculated width, so the data is formatted nicely.</li><li>Introduced <code>UnitOfWorkFactory</code> to allow end users to use custom <code>Un
 itOfWork</code> implementations created by the factory.</li><li>Doing request/reply over <a shape="rect" href="jms.html">JMS</a> allows per individual message <code>requestTimeout</code> value by specifying the timeout value in the <code>"CamelJmsRequestTimeout"</code> header.</li><li><a shape="rect" href="quartz.html">Quartz</a> and <a shape="rect" href="quartz2.html">Quartz2</a> components now enlist the quartz scheduler by default in JMX, unless configured to be disabled.</li><li><span><a shape="rect" href="twitter.html">Twitter</a> Component supports to set proxy.</span></li></ul><h3 id="Camel2.13.0Release-FixedIssues">Fixed Issues</h3><ul><li>Fixed an <code>ArrayIndexOutOfBoundsException</code> with <a shape="rect" href="message-history.html">Message History</a> when using <a shape="rect" href="seda.html">SEDA</a></li><li>Fixed <code>requestTimeout</code> on <a shape="rect" href="netty.html">Netty</a> not triggering when we have received message.</li><li>Fixed <a shape="rect" h
 ref="parameter-binding-annotations.html">Parameter Binding Annotations</a> on boolean types to evaluate as <a shape="rect" href="predicate.html">Predicate</a> instead of <a shape="rect" href="expression.html">Expression</a></li><li>Fixed using <a shape="rect" href="file2.html">File</a> consumer with <code>delete=true&amp;readLock=fileLock</code> not being able to delete the file on Windows.</li><li>Fixed <a shape="rect" href="throttler.html">Throttler</a> to honor time slots after period expires (eg so it works consistently and as expected).</li><li>Fixed getting JMSXUserID property when consuming from <a shape="rect" href="activemq.html">ActiveMQ</a></li><li>Fixed <a shape="rect" href="intercept.html">interceptFrom</a> to support property placeholders</li><li>Fixed a race condition in initializing <code>SSLContext</code> in <a shape="rect" href="netty.html">Netty</a> and <a shape="rect" href="netty-http.html">Netty HTTP</a></li><li>Fixed using <a shape="rect" href="recipient-list.h
 tml">Recipient List</a>, <a shape="rect" href="routing-slip.html">Routing Slip</a> calling another route which is configured with <code>NoErrorHandler</code>, and an exception occurred in that route, would be propagated back as not-exhausted, allow the caller route to have its error handler react on the exception.</li><li>Fixed <a shape="rect" href="quartz.html">Quartz</a> and exception was thrown when scheduling a job, would affect during shutdown, assuming the job was still in progress, and not shutdown the Quartz scheduler.</li><li>Fixed so you can configure <a shape="rect" href="stomp.html">Stomp</a> endpoints using <a shape="rect" href="uris.html">URIs</a></li><li>Fixed memory leak when using <a shape="rect" href="language.html">Language</a> component with <code>camel-script</code> languages and having <code>contentCache=false</code></li><li>Fixed <a shape="rect" href="error-handler.html">Error Handler</a> may log at <code>WARN</code> level "Cannot determine current route from 
 Exchange" when using <a shape="rect" href="splitter.html">Splitter</a></li><li>Fixed <code>camel-fop</code> to work in Apache <a shape="rect" href="karaf.html">Karaf</a> and ServiceMix</li><li>Fixed <a shape="rect" href="hdfs.html">HDFS</a> producer to use the configured <a shape="rect" href="uuidgenerator.html">UuidGenerator</a> when generating split file names to avoid filename collisions</li><li>Fixed <code>JpaProducer</code> and <code>JpaConsumer</code> of the <a shape="rect" href="jpa.html">JPA</a> component to not share/reuse the same <code>EntityManager</code> object which could cause problems if this would occur in the context of multiple/different threads.</li><li>Fixed <a shape="rect" href="http4.html">HTTP4</a> to support multiple custom component names in use, each configured using different <code>SSLContext</code>.</li><li>Fixed <a shape="rect" href="content-based-router.html">Content Based Router</a> using method call's as <a shape="rect" href="predicate.html">Predicat
 e</a>s if threw an exception, the <a shape="rect" href="content-based-router.html">Content Based Router</a> will call next predicate before triggering <a shape="rect" href="error-handler.html">Error Handler</a>.</li><li>Fixed <a shape="rect" href="netty-http.html">Netty HTTP</a> producer with query parameters may use wrong parameters from a previous call.</li><li>Fixed <a shape="rect" href="netty.html">Netty</a> producer may cause <code>NullPointerException</code> in <code>messageReceived</code> in client handler, if a <code>Channel</code> was destroyed from the producer pool.</li><li>Fixed <a shape="rect" href="file2.html">File</a> and <a shape="rect" href="ftp2.html">FTP</a> consumer(s) when <code>idempotent=true</code> could not detect changed file(s) as a new file, but would regard the file as idempotent.</li><li>Fixed <a shape="rect" href="stream.html">Stream</a> consumer reading a file using <code>groupLines</code> would not read last group of message if there was not enough l
 ines to hit the threshold.</li><li>Fixed deleting the <em>done file</em> if <a shape="rect" href="file2.html">File</a> or <a shape="rect" href="ftp2.html">FTP</a> consumer rollback and the <code>moveFailed</code> option is in use.</li><li>Fixed <a shape="rect" href="avro.html">avro</a> data format in OSGi not being able to load schema classes.</li><li>Fixed <a shape="rect" href="camel-jmx.html">JMX</a> when using custom beans in routes with <code>@ManagedResource</code> to expose JMX attributes/operations to not include Camel standard attributes/operations from its processors, which would be shown as unavailable in JMX consoles.</li><li>Fixed <a shape="rect" href="quartz2.html">Quartz2</a> simple trigger repeat count default value not working causing the trigger to only fire once, instead of forever.</li></ul><h3 id="Camel2.13.0Release-New">New <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a></h3><h3 id="Camel2.13.0Release-New.1">New <a
  shape="rect" href="components.html">Components</a></h3><ul><li><a shape="rect" href="infinispan.html"><code>camel-infinispan</code></a> - to interact with <a shape="rect" class="external-link" href="http://www.infinispan.org/" rel="nofollow">Infinispan</a> distributed data grid / cache.</li><li><a shape="rect" href="optaplanner.html"><code>camel-optaplanner</code></a> - to use <a shape="rect" class="external-link" href="http://www.optaplanner.org/" rel="nofollow">OptaPlanner</a> for problem solving plans.</li><li><a shape="rect" href="splunk.html"><code>camel-splunk</code></a> - enables you to publish and search for events in Splunk</li></ul><h3 id="Camel2.13.0Release-New.2">New <a shape="rect" href="camel-maven-archetypes.html">Camel Maven Archetypes</a></h3><ul><li>camel-archetype-cxf-code-first-blueprint</li><li>camel-archetype-cxf-contract-first-blueprint</li></ul><h3 id="Camel2.13.0Release-NewDSL">New DSL</h3><h3 id="Camel2.13.0Release-NewAnnotations">New Annotations</h3><ul><
 li><a shape="rect" href="bean-injection.html"><code>@BeanInject</code></a></li></ul><h3 id="Camel2.13.0Release-NewDataFormats">New <a shape="rect" href="data-format.html">Data Formats</a></h3><h3 id="Camel2.13.0Release-New.3">New <a shape="rect" href="languages.html">Languages</a></h3><ul><li><a shape="rect" href="jsonpath.html">JSonPath</a> - To perform <a shape="rect" href="expression.html">Expression</a> and <a shape="rect" href="predicate.html">Predicate</a> on json payloads.</li></ul><h3 id="Camel2.13.0Release-New.4">New <a shape="rect" href="examples.html">Examples</a></h3><h3 id="Camel2.13.0Release-New.5">New <a shape="rect" href="tutorials.html">Tutorials</a></h3><h3 id="Camel2.13.0Release-NewTooling">New Tooling</h3><h2 id="Camel2.13.0Release-APIchanges">API changes</h2><h2 id="Camel2.13.0Release-KnownIssues">Known Issues</h2><h2 id="Camel2.13.0Release-DependencyUpgrades">Dependency Upgrades</h2><p>You can see any dependency changes using <a shape="rect" class="external-lin
 k" href="http://vdiff.notsoclever.cc/" rel="nofollow">Camel Dependencies Version Differences web tool</a> created by Tracy Snell from the Camel <a shape="rect" href="team.html">Team</a>.</p><p>The below list is a best effort, and we may miss some updates, its better to use the <a shape="rect" class="external-link" href="http://vdiff.notsoclever.cc/" rel="nofollow">Camel Dependencies Version Differences web tool</a> which uses the released projects for comparison.</p><ul><li>AHC 1.7.20 to 1.7.21</li><li>APNS 0.1.6 to 0.2.3</li><li>AWS-SDK 1.5.1 to 1.6.3</li><li>Avro 1.7.3 to 1.7.5</li><li>BeanIO 2.0.6 to 2.0.7</li><li>CXF 2.7.6 to 2.7.8</li><li>EHCache 2.7.2 to 2.7.4</li><li>Elasticsearch 0.20.6 to 0.90.5</li><li>FOP 1.0 to 1.1</li><li>Guave 14.0.1 to 15.0</li><li>Hazelcast 2.6 to 3.0.2</li><li>ICal4j 1.0.4 to 1.0.5.2</li><li>Jclouds 1.6.2-incubating to 1.6.3</li><li>Jetty 7.6.9 to 8.1.12</li><li>Joda time 2.1 to 2.3</li><li>JRuby 1.7.4 to 1.7.5</li><li>Lucene 3.6.0 to 4.5.1</li><li>
 MongoDB Java Driver 2.11.2 to 2.11.3</li><li>Quartz 2.2.0 to 2.2.1</li><li>Restlet 2.0.15 to 2.1.4</li><li>Saxon 9.5.0.2 to 9.5.1-2</li><li>Scala 2.10.2 to 2.10.3</li><li>Servlet API 2.5 to 3.0</li><li>SolrJ 3.6.2 to 4.5.1</li><li>Spring Batch 2.2.1.RELEASE to 2.2.2.RELEASE</li><li>Spring Redis 1.0.4.RELEASE to 1.1.0.RELEASE</li><li>SSHD 0.8.0 to 0.9.0</li><li>TestNG 6.8.5 to 6.8.7</li></ul><h2 id="Camel2.13.0Release-Internalchanges">Internal changes</h2><ul><li>Add <code>RouteAware</code> API to inject <code>Route</code> for <code>Service</code>'s in routes, for example the <code>Consumer</code>'s of the routes.</li><li><code>IOHelper.gerCharsetName</code> will now lookup key <code>Exchange.CHARSET_NAME</code> in header first and then fallback to property.</li><li>Camel Spring now longer automatic registers "spring-event://default" endpoint, which wasnt in use anyway.&#160;</li></ul><h2 id="Camel2.13.0Release-Changesthatmayaffectendusers">Changes that may affect end users</h2><ul><
 li>Components depending on Servlet API has been upgrade from Servlet API 2.5 to 3.0</li><li>Jetty upgraded from 7.6.x to 8.1.x</li><li><a shape="rect" href="hazelcast-component.html">Hazelcast Component</a> uses <code>Object</code> instead of <code>String</code> as the key.</li><li><a shape="rect" href="hazelcast-component.html">Hazelcast Component</a> atomic number producer was using incorrect name (<a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-6833">CAMEL-6833</a>). Name will be different with this release.</li><li><a shape="rect" href="hazelcast-component.html">Hazelcast Component</a> instance consumer was incorrectly writing headers to the "out" message as opposed to the "in" message. Headers are now written to the "in" message.</li><li><a shape="rect" href="hazelcast-component.html">Hazelcast Component</a> map/multimap consumer were sending header value "envict" when an item was evicted. This has been corrected and the value "evicted" i
 s used now.</li><li>The enum value <code>NON_BLOCKING</code> has been removed in <code>camel-apns</code> as its no longer support in APNS itself.</li><li><code>DefaultTimeoutMap</code> must call <code>start</code> to initialize the map before use.</li><li><code>@ExcludeRoutes</code> test annotation now accepts only classes implementing <code>RoutesBuilder</code> interface.</li><li>The MBean names registered by <a shape="rect" href="camel-jmx.html">Camel JMX</a> no longer include the hostname in the <code>context</code> part, eg before <code>context=myHost/myCamelId</code> and now after <code>context=myCamelId</code>. Having the hostname in the MBean name does not bring much value, and in fact makes things more complicated as the mbean name changes depending on the host running Camel. There is an option <code>includeHostName</code> that can be configure as <code>true</code> to preserve the old behavior.</li><li><a shape="rect" href="camel-jmx.html">MBean naming</a> in OSGi cleaned up
  to use simpler naming with symbolicName. Before we could have MBean names with duplicate bundle ids such as <code>context=114-114-camel-6</code>, which now is using the symbolic name instead, <code>context=MyApplication</code>.</li><li>Added <code>beforeAddRoutes</code> and <code>afterAddRoutes</code> to <code>org.apache.camel.component.servletlistener.CamelContextLifecycle</code> in <a shape="rect" href="servletlistener-component.html">ServletListener Component</a></li><li>The <a shape="rect" href="language.html">Language</a> component now no longer caches the compiled script as that could cause side-effects. You can set <code>cacheScript=true</code> to enable the previous behavior if your script is safe to do so.</li><li>The default value of <code>urlDecodeHeaders</code> option on <a shape="rect" href="netty-http.html">Netty HTTP</a> has been changed from <code>true</code> to <code>false</code>.</li></ul><h2 id="Camel2.13.0Release-Importantchangestoconsiderwhenupgrading">Importan
 t changes to consider when upgrading</h2><ul><li>If using <code>groupedExchanges</code> option on <a shape="rect" href="aggregator2.html">Aggregate</a> EIP then the <a shape="rect" href="exchange.html">Exchange</a>s is now stored on the message body as well. The old way of storing as a property is considered deprecated. See more details at <a shape="rect" href="aggregator2.html">Aggregate</a>.</li></ul><h2 id="Camel2.13.0Release-GettingtheDistributions">Getting the Distributions</h2><h3 id="Camel2.13.0Release-BinaryDistributions">Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluen
 ceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.13.0/apache-camel-2.13.0.zip">apache-camel-2.13.0.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/camel/apache-camel/2.13.0/apache-camel-2.13.0.zip.asc">apache-camel-2.13.0.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.13.0/apache-camel-2.13.0.tar.gz">apache-camel-2.13.0.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/camel/apache-camel/2.13.0/apache-camel-2.13.0.tar.gz.asc">apache-camel-2.13.0.tar.gz.asc</a></p></td></tr></tbody></table></div>    <div class="aui-messa
 ge hint shadowed information-macro">
                     <p class="title">The above URLs use redirection</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">

Modified: websites/production/camel/content/hl7.html
==============================================================================
--- websites/production/camel/content/hl7.html (original)
+++ websites/production/camel/content/hl7.html Tue Dec 17 20:19:28 2013
@@ -85,71 +85,33 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="HL7-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;
+<div class="wiki-content maincontent"><h2 id="HL7-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></u
 l><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-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="HL7-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="HL7-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="HL7-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="HL7-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;
 
@@ -163,53 +125,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="HL7-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="HL7-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="HL7-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="HL7-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 pati
 ent 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="HL7-HL7DataFormat">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="HL7-HL7DataFormat">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>
 
@@ -262,38 +194,13 @@ Then you don't need to create an instanc
                     </div>
     </div>
 
-
-
-<h3 id="HL7-MessageHeaders">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="HL7-MessageHeaders">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="HL7-Options">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="HL7-Options">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="HL7-Dependencies">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="HL7-Dependencies">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 t
 hemselves. 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;
@@ -306,30 +213,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="HL7-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="HL7-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
@@ -343,19 +235,8 @@ import static org.apache.camel.component
       .to(&quot;mock:test2&quot;);
 
 ]]></script>
-</div></div>
-
-
-<h3 id="HL7-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="HL7-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;
 ...
 
@@ -365,17 +246,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="HL7-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="HL7-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;
 ...
@@ -394,12 +266,7 @@ import ca.uhn.hl7v2.validation.impl.Defa
       // acknowledgement
       .transform(ack())
 ]]></script>
-</div></div>
-
-
-<h3 id="HL7-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="HL7-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;;
@@ -411,12 +278,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 {
 
@@ -438,10 +300,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
@@ -468,14 +327,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="HL7-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="HL7-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="co
 de 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;);
@@ -488,10 +340,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() {
@@ -506,9 +355,7 @@ from(&quot;mina2:tcp://127.0.0.1:8888?sy
     })
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<h3 id="HL7-SeeAlso">See Also</h3>
+</div></div><p></p><h3 id="HL7-SeeAlso">See Also</h3>
 <ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul></div>
         </td>
         <td valign="top">



Mime
View raw message