camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r917090 [2/3] - in /websites/production/camel/content: book-dataformat-appendix.html book-in-one-page.html cache/main.pageCache json.html
Date Tue, 22 Jul 2014 12:18:34 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 Tue Jul 22 12:18:33 2014
@@ -552,7 +552,10 @@ Camel uses a Java based <a shape="rect" 
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses the <a shape="rect" href="bean-binding.html">Bean Binding</a> to bind message exchanges to beans in the <a shape="rect" href="registry.html">Registry</a>. Is also used for exposing and invoking POJO (Plain Old Java Objects).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="bean-validator.html">Bean Validator</a> / camel-bean-validator</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[bean-validator:label[?options]
 ]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Validates the payload of a message using the Java Validation API (<a shape="rect" class="external-link" href="http://jcp.org/en/jsr/detail?id=303" rel="nofollow">JSR 303</a> and JAXP Validation) and its reference implementation <a shape="rect" class="external-link" href="http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/" rel="nofollow">Hibernate Validator</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="browse.html">Browse</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Validates the payload of a message using the Java Validation API (<a shape="rect" class="external-link" href="http://jcp.org/en/jsr/detail?id=303" rel="nofollow">JSR 303</a> and JAXP Validation) and its reference implementation <a shape="rect" class="external-link" href="http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/" rel="nofollow">Hibernate Validator</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="box.html">Box</a> / camel-box</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[box://endpoint-prefix/endpoint?[options]
+]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For uploading, downloading and managing files, managing files, folders, groups, collaborations, etc. on Box.com.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="browse.html">Browse</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[browse:someName
 ]]></script>
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Provides a simple <a shape="rect" href="browsableendpoint.html">BrowsableEndpoint</a> which can be useful for testing, visualisation tools or debugging. The exchanges sent to the endpoint are all available to be browsed.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cache.html">Cache</a> / camel-cache</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -607,7 +610,9 @@ Camel uses a Java based <a shape="rect" 
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[disruptor:someName[?&lt;option&gt;]
 disruptor-vm:someName[?&lt;option&gt;]
 ]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To provide the implementation of <a shape="rect" href="seda.html">SEDA</a> which is based on <a shape="rect" class="external-link" href="https://github.com/LMAX-Exchange/disruptor" rel="nofollow">disruptor</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="ejb.html">EJB</a> / camel-ejb</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To provide the implementation of <a shape="rect" href="seda.html">SEDA</a> which is based on <a shape="rect" class="external-link" href="https://github.com/LMAX-Exchange/disruptor" rel="nofollow">disruptor</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="disruptor.html">D</a><a shape="rect" href="dropbox.html">ropbox</a><span> / camel-dropbox</span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[dropbox://[operation]?[options]]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><span style="color: rgb(0,0,0);">The&#160;</span><strong>dropbox:</strong><span style="color: rgb(0,0,0);">&#160;component allows you to treat&#160;</span><a shape="rect" class="external-link" href="https://www.dropbox.com/" rel="nofollow">Dropbox</a><span style="color: rgb(0,0,0);">&#160;remote folders as a producer or consumer of messages.</span></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="ejb.html">EJB</a> / camel-ejb</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[ejb:ejbName[?options]
 ]]></script>
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses the <a shape="rect" href="bean-binding.html">Bean Binding</a> to bind message exchanges to EJBs. It works like the <a shape="rect" href="bean.html">Bean</a> component but just for accessing EJBs. Supports EJB 3.0 onwards.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="elasticsearch.html">ElasticSearch</a> / camel-elasticsearch</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -747,7 +752,10 @@ disruptor-vm:someName[?&lt;option&gt;]
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Executes <a shape="rect" href="languages.html">Languages</a> scripts</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="ldap.html">LDAP</a> / camel-ldap</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[ldap:host[:port][?options]
 ]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Performing searches on LDAP servers (&lt;scope&gt; must be one of object|onelevel|subtree)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="log.html">Log</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Performing searches on LDAP servers (&lt;scope&gt; must be one of object|onelevel|subtree)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="linkedin.html">LinkedIn</a> / camel-linkedin</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[linkedin://endpoint-prefix/endpoint?[options]
+]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Component for retrieving LinkedIn user profiles, connections, companies, groups, posts, etc. using LinkedIn REST API.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="log.html">Log</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[log:loggingCategory[?options]
 ]]></script>
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses Jakarta Commons Logging to log the message exchange to some underlying logging system like log4j</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="lucene.html">Lucene</a> / camel-lucene</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -825,7 +833,9 @@ disruptor-vm:someName[?&lt;option&gt;]
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Component for integrating with RabbitMQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="ref.html">Ref</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[ref:name
 ]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Component for lookup of existing endpoints bound in the <a shape="rect" href="registry.html">Registry</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="restlet.html">Restlet</a> / camel-restlet</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Component for lookup of existing endpoints bound in the <a shape="rect" href="registry.html">Registry</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="rest.html">Rest</a> / camel-core</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[rest:verb:path[?options]]]></script>
+</div></div></td><td colspan="1" rowspan="1" class="confluenceTd">Component for consuming Restful resources supporting the <a shape="rect" href="component-list.html">Rest DSL</a> and plugins to other Camel rest components.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="restlet.html">Restlet</a> / camel-restlet</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: plain; gutter: false" type="syntaxhighlighter"><![CDATA[restlet:restletUrl[?options]
 ]]></script>
 </div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Component for consuming and producing Restful resources using <a shape="rect" class="external-link" href="http://www.restlet.org" rel="nofollow">Restlet</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="rmi.html">RMI</a> / camel-rmi</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -4143,11 +4153,11 @@ While not actual tutorials you might fin
                     </div>
     </div>
 <h2 id="BookInOnePage-Preface">Preface</h2><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><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1404980247242 {padding: 0px;}
-div.rbtoc1404980247242 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1404980247242 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1406031449524 {padding: 0px;}
+div.rbtoc1406031449524 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1406031449524 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1404980247242">
+/*]]>*/</style></p><div class="toc-macro rbtoc1406031449524">
 <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>
@@ -6333,11 +6343,11 @@ So we completed the last piece in the pi
 
 
 <style type="text/css">/*<![CDATA[*/
-div.rbtoc1404980247615 {padding: 0px;}
-div.rbtoc1404980247615 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1404980247615 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1406031449867 {padding: 0px;}
+div.rbtoc1406031449867 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1406031449867 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style><div class="toc-macro rbtoc1404980247615">
+/*]]>*/</style><div class="toc-macro rbtoc1406031449867">
 <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>
@@ -11215,7 +11225,19 @@ from(&quot;direct:inPojoAgeView&quot;).
     &lt;json library=&quot;Jackson&quot; unmarshalTypeName=&quot;org.apache.camel.component.jackson.TestPojoView&quot; jsonView=&quot;org.apache.camel.component.jackson.Views$Age&quot;/&gt;
   &lt;/marshal&gt;
 ]]></script>
-</div></div><h3 id="BookInOnePage-DependenciesforXStream">Dependencies for XStream</h3><p>To use JSON in your camel routes you need to add the a dependency on <strong>camel-xstream</strong> which implements this data format.</p><p>If you use maven you could just add the following to your pom.xml, substituting the version number for the latest &amp; greatest release (see <a shape="rect" href="download.html">the download page for the latest versions</a>).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookInOnePage-SettingserializationincludeoptionforJacksonmarshal">Setting serialization include option for Jackson marshal</h3><p><strong>Available as of Camel 2.13.3/2.14</strong></p><p>If you want to marshal a pojo to JSON, and the pojo has some fields with null values. And you want to skip these null values, then you need to set either an annotation on the pojo,&#160;</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[@JsonInclude(Include.NON_NULL)
+public class MyPojo {
+   ...
+}]]></script>
+</div></div><p>But this requires you to include that annotation in your pojo source code. You can also configure the Camel JsonDataFormat to set the include option, 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[JacksonDataFormat format = new JacksonDataFormat();
+format.setInclude(&quot;NON_NULL&quot;);]]></script>
+</div></div><p>Or from XML DSL you configure this as</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[    &lt;dataFormats&gt;
+      &lt;json id=&quot;json&quot; library=&quot;Jackson&quot; include=&quot;NOT_NULL&quot;/&gt;
+    &lt;/dataFormats&gt;]]></script>
+</div></div><p>&#160;</p><h3 id="BookInOnePage-DependenciesforXStream">Dependencies for XStream</h3><p>To use JSON in your camel routes you need to add the a dependency on <strong>camel-xstream</strong> which implements this data format.</p><p>If you use maven you could just add the following to your pom.xml, substituting the version number for the latest &amp; greatest release (see <a shape="rect" href="download.html">the download page for the latest versions</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;org.apache.camel&lt;/groupId&gt;
   &lt;artifactId&gt;camel-xstream&lt;/artifactId&gt;
@@ -14886,7 +14908,7 @@ from(&quot;activemq:my.queue&quot;).spli
                     <p class="title">Splitting big XML payloads</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">
-                            <p>The XPath engine in Java and <a shape="rect" href="xquery.html">saxon</a> will load the entire XML content into memory. And thus they are not well suited for very big XML payloads.<br clear="none"> Instead you can use a custom <a shape="rect" href="expression.html">Expression</a> which will iterate the XML payload in a streamed fashion. From Camel 2.9 onwards you can use the Tokenizer language<br clear="none"> which supports this when you supply the start and end tokens.</p>
+                            <p>The XPath engine in Java and <a shape="rect" href="xquery.html">saxon</a> will load the entire XML content into memory. And thus they are not well suited for very big XML payloads.<br clear="none"> Instead you can use a custom <a shape="rect" href="expression.html">Expression</a> which will iterate the XML payload in a streamed fashion. From Camel 2.9 onwards you can use the Tokenizer language<br clear="none"> which supports this when you supply the start and end tokens. From Camel 2.14, you can use the XMLTokenizer language which is <span>specifically </span>provided for tokenizing XML documents.</p>
                     </div>
     </div>
 <p>You can split streams by enabling the streaming mode using the <code>streaming</code> builder method.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -14952,7 +14974,7 @@ from(&quot;direct:streaming&quot;)
     .split().tokenizeXML(&quot;order&quot;, &quot;orders&quot;).streaming()
        .to(&quot;activemq:queue:order&quot;);
 ]]></script>
-</div></div><p><span style="line-height: 1.4285715;">Available as of Camel 2.13.1, you can set the above inheritNamsepaceTagName property to "*" to&#160;include the preceding context in each token (i.e., generating each token enclosed in its ancestor elements). It is noted that each token must share the same ancestor elements in this case.</span></p><p><span style="line-height: 1.4285715;">The above tokenizer works well on simple structures but has some inherent limitations in handling more complex XML structures.</span></p><p><strong>Available as of Camel 2.14</strong></p><p>The second tokenizer that uses a StAX parser to overcome these limitations. This tokenizer recognizes XML namespaces and also complex XML structures.</p><p>To split using this tokenizer at {<a shape="rect" rel="nofollow">urn:shop}order</a>, we can write</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p><span style="line-height: 1.4285715;">Available as of Camel 2.13.1, you can set the above inheritNamsepaceTagName property to "*" to&#160;include the preceding context in each token (i.e., generating each token enclosed in its ancestor elements). It is noted that each token must share the same ancestor elements in this case.</span></p><p><span style="line-height: 1.4285715;">The above tokenizer works well on simple structures but has some inherent limitations in handling more complex XML structures.</span></p><p><strong>Available as of Camel 2.14</strong></p><p>The second tokenizer uses a StAX parser to overcome these limitations. This tokenizer recognizes XML namespaces and also handles simple and complex XML structures more naturally and efficiently.&#160;</p><p>To split using this tokenizer at {<a shape="rect" rel="nofollow">urn:shop}order</a>, we can write</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[  Namespaces ns = new Namespaces(&quot;ns1&quot;, &quot;urn:shop&quot;);
   ...
   from(&quot;file:inbox&quot;)
@@ -20090,11 +20112,11 @@ template.send(&quot;direct:alias-verify&
                     </div>
     </div>
 <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><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1404980262814 {padding: 0px;}
-div.rbtoc1404980262814 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1404980262814 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1406031459661 {padding: 0px;}
+div.rbtoc1406031459661 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1406031459661 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1404980262814">
+/*]]>*/</style></p><div class="toc-macro rbtoc1406031459661">
 <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>
@@ -28889,184 +28911,97 @@ properties:key[?options]
     </div>
 
 
-<h2 id="BookInOnePage-UsingPropertyPlaceholder">Using PropertyPlaceholder</h2>
-<p><strong>Available as of Camel 2.3</strong></p>
-
-<p>Camel now provides a new <code>PropertiesComponent</code> in <strong>camel-core</strong> which allows you to use property placeholders when defining Camel <a shape="rect" href="endpoint.html">Endpoint</a> URIs. <br clear="none">
-This works much like you would do if using Spring's <code>&lt;property-placeholder&gt;</code> tag. However Spring have a limitation which prevents 3rd party frameworks to leverage Spring property placeholders to the fullest. See more at <a shape="rect" href="how-do-i-use-spring-property-placeholder-with-camel-xml.html">How do I use Spring Property Placeholder with Camel XML</a>.</p>
-
-    <div class="aui-message success shadowed information-macro">
+<h2 id="BookInOnePage-UsingPropertyPlaceholder">Using PropertyPlaceholder</h2><p><strong>Available as of Camel 2.3</strong></p><p>Camel now provides a new <code>PropertiesComponent</code> in <strong>camel-core</strong> which allows you to use property placeholders when defining Camel <a shape="rect" href="endpoint.html">Endpoint</a> URIs. <br clear="none"> This works much like you would do if using Spring's <code>&lt;property-placeholder&gt;</code> tag. However Spring have a limitation which prevents 3rd party frameworks to leverage Spring property placeholders to the fullest. See more at <a shape="rect" href="how-do-i-use-spring-property-placeholder-with-camel-xml.html">How do I use Spring Property Placeholder with Camel XML</a>.</p>    <div class="aui-message success shadowed information-macro">
                     <p class="title">Bridging Spring and Camel property placeholders</p>
                             <span class="aui-icon icon-success">Icon</span>
                 <div class="message-content">
-                            
-<p>From Camel 2.10 onwards, you can bridge the Spring property placeholder with Camel, see further below for more details.</p>
+                            <p>From Camel 2.10 onwards, you can bridge the Spring property placeholder with Camel, see further below for more details.</p>
                     </div>
     </div>
-
-
-<p>The property placeholder is generally in use when doing:</p>
-<ul class="alternate"><li>lookup or creating endpoints</li><li>lookup of beans in the <a shape="rect" href="registry.html">Registry</a></li><li>additional supported in Spring XML (see below in examples)</li><li>using Blueprint PropertyPlaceholder with Camel <a shape="rect" href="properties.html">Properties</a> component</li><li>using <code>@PropertyInject</code> to inject a property in a POJO</li></ul>
-
-
-<h3 id="BookInOnePage-Syntax.1">Syntax</h3>
-<p>The syntax to use Camel's property placeholder is to use {{<code>key</code>}} for example {{<code>file.uri</code>}} where <code>file.uri</code> is the property key.<br clear="none">
-You can use property placeholders in parts of the endpoint URI's which for example you can use placeholders for parameters in the URIs.</p>
-
-<h3 id="BookInOnePage-PropertyResolver">PropertyResolver</h3>
-<p>Camel provides a pluggable mechanism which allows 3rd part to provide their own resolver to lookup properties. Camel provides a default implementation <code>org.apache.camel.component.properties.DefaultPropertiesResolver</code> which is capable of loading properties from the file system, classpath or <a shape="rect" href="registry.html">Registry</a>. You can prefix the locations with either:</p>
-<ul class="alternate"><li><code>ref:</code> <strong>Camel 2.4:</strong> to lookup in the <a shape="rect" href="registry.html">Registry</a></li><li><code>file:</code> to load the from file system</li><li><code>classpath:</code> to load from classpath (this is also the default if no prefix is provided)</li><li><code>blueprint:</code> <strong>Camel 2.7:</strong> to use a specific OSGi blueprint placeholder service</li></ul>
-
-
-<h3 id="BookInOnePage-Defininglocation">Defining location</h3>
-<p>The <code>PropertiesResolver</code> need to know a location(s) where to resolve the properties. You can define 1 to many locations. If you define the location in a single String property you can separate multiple locations with comma such as:</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[
-pc.setLocation(&quot;com/mycompany/myprop.properties,com/mycompany/other.properties&quot;);
+<p>The property placeholder is generally in use when doing:</p><ul class="alternate"><li>lookup or creating endpoints</li><li>lookup of beans in the <a shape="rect" href="registry.html">Registry</a></li><li>additional supported in Spring XML (see below in examples)</li><li>using Blueprint PropertyPlaceholder with Camel <a shape="rect" href="properties.html">Properties</a> component</li><li>using <code>@PropertyInject</code> to inject a property in a POJO</li></ul><h3 id="BookInOnePage-Syntax.1">Syntax</h3><p>The syntax to use Camel's property placeholder is to use {{<code>key</code>}} for example {{<code>file.uri</code>}} where <code>file.uri</code> is the property key.<br clear="none"> You can use property placeholders in parts of the endpoint URI's which for example you can use placeholders for parameters in the URIs.</p><h3 id="BookInOnePage-PropertyResolver">PropertyResolver</h3><p>Camel provides a pluggable mechanism which allows 3rd part to provide their own resolver to lookup
  properties. Camel provides a default implementation <code>org.apache.camel.component.properties.DefaultPropertiesResolver</code> which is capable of loading properties from the file system, classpath or <a shape="rect" href="registry.html">Registry</a>. You can prefix the locations with either:</p><ul class="alternate"><li><code>ref:</code> <strong>Camel 2.4:</strong> to lookup in the <a shape="rect" href="registry.html">Registry</a></li><li><code>file:</code> to load the from file system</li><li><code>classpath:</code> to load from classpath (this is also the default if no prefix is provided)</li><li><code>blueprint:</code> <strong>Camel 2.7:</strong> to use a specific OSGi blueprint placeholder service</li></ul><h3 id="BookInOnePage-Defininglocation">Defining location</h3><p>The <code>PropertiesResolver</code> need to know a location(s) where to resolve the properties. You can define 1 to many locations. If you define the location in a single String property you can separate mult
 iple locations with comma such as:</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[pc.setLocation(&quot;com/mycompany/myprop.properties,com/mycompany/other.properties&quot;);
 ]]></script>
-</div></div>
-
-<h4 id="BookInOnePage-Usingsystemandenvironmentvariablesinlocations">Using system and environment variables in locations</h4>
-<p><strong>Available as of Camel 2.7</strong></p>
-
-<p>The location now supports using placeholders for JVM system properties and OS environments variables.</p>
-
-<p>For 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[
-location=file:${karaf.home}/etc/foo.properties
+</div></div><h4 id="BookInOnePage-Usingsystemandenvironmentvariablesinlocations">Using system and environment variables in locations</h4><p><strong>Available as of Camel 2.7</strong></p><p>The location now supports using placeholders for JVM system properties and OS environments variables.</p><p>For 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[location=file:${karaf.home}/etc/foo.properties
 ]]></script>
-</div></div>
-
-<p>In the location above we defined a location using the file scheme using the JVM system property with key <code>karaf.home</code>.</p>
-
-<p>To use an OS environment variable instead you would have to prefix with env:</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[
-location=file:${env:APP_HOME}/etc/foo.properties
+</div></div><p>In the location above we defined a location using the file scheme using the JVM system property with key <code>karaf.home</code>.</p><p>To use an OS environment variable instead you would have to prefix with env:</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[location=file:${env:APP_HOME}/etc/foo.properties
 ]]></script>
-</div></div>
-<p>Where <code>APP_HOME</code> is an OS environment.</p>
-
-<p>You can have multiple placeholders in the same location, such as:</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[
-location=file:${env:APP_HOME}/etc/${prop.name}.properties
+</div></div><p>Where <code>APP_HOME</code> is an OS environment.</p><p>You can have multiple placeholders in the same location, such as:</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[location=file:${env:APP_HOME}/etc/${prop.name}.properties
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-ConfiguringinJavaDSL">Configuring in Java DSL</h3>
-<p>You have to create and register the <code>PropertiesComponent</code> under the name <code>properties</code> such as:</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[
-PropertiesComponent pc = new PropertiesComponent();
+</div></div><h4 id="BookInOnePage-Usingsystemandenvironmentvariablestoconfigurepropertyprefixesandsuffixes">Using system and environment variables to configure property prefixes and suffixes</h4><p><strong>Available as of Camel 2.12.5, 2.13.3, 2.14.0</strong></p><p><code>propertyPrefix</code>, <code>propertySuffix</code> configuration properties support using placeholders for JVM system properties and OS environments variables.</p><p>For example. if&#160;<code>PropertiesComponent</code> is configured with the following properties file:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
+<pre>dev.endpoint = result1
+test.endpoint = result2</pre>
+</div></div><p>Then with the following route definition:</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[PropertiesComponent pc = context.getComponent(&quot;properties&quot;, PropertiesComponent.class);
+pc.setPropertyPrefix(&quot;${stage}.&quot;);
+// ...
+context.addRoutes(new RouteBuilder() {
+    @Override
+    public void configure() throws Exception {
+        from(&quot;direct:start&quot;).to(&quot;properties:mock:{{endpoint}}&quot;);
+    }
+});]]></script>
+</div></div><p>it is possible to change the target endpoint by changing system property&#160;<code>stage</code> either to&#160;<code>dev</code> (the message will be routed to&#160;<code>mock:result1</code>) or&#160;<code>test</code> (the message will be routed to&#160;<code>mock:result2</code>).</p><h3 id="BookInOnePage-ConfiguringinJavaDSL">Configuring in Java DSL</h3><p>You have to create and register the <code>PropertiesComponent</code> under the name <code>properties</code> such as:</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[PropertiesComponent pc = new PropertiesComponent();
 pc.setLocation(&quot;classpath:com/mycompany/myprop.properties&quot;);
 context.addComponent(&quot;properties&quot;, pc);
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-ConfiguringinSpringXML">Configuring in Spring XML</h3>
-<p>Spring XML offers two variations to configure. You can define a spring bean as a <code>PropertiesComponent</code> which resembles the way done in Java DSL. Or you can use the <code>&lt;propertyPlaceholder&gt;</code> 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;bean id=&quot;properties&quot; class=&quot;org.apache.camel.component.properties.PropertiesComponent&quot;&gt;
+</div></div><h3 id="BookInOnePage-ConfiguringinSpringXML">Configuring in Spring XML</h3><p>Spring XML offers two variations to configure. You can define a spring bean as a <code>PropertiesComponent</code> which resembles the way done in Java DSL. Or you can use the <code>&lt;propertyPlaceholder&gt;</code> 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;bean id=&quot;properties&quot; class=&quot;org.apache.camel.component.properties.PropertiesComponent&quot;&gt;
     &lt;property name=&quot;location&quot; value=&quot;classpath:com/mycompany/myprop.properties&quot;/&gt;
 &lt;/bean&gt;
 ]]></script>
-</div></div>
-
-<p>Using the <code>&lt;propertyPlaceholder&gt;</code> tag makes the configuration a bit more fresh such 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;camelContext ...&gt;
+</div></div><p>Using the <code>&lt;propertyPlaceholder&gt;</code> tag makes the configuration a bit more fresh such 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;camelContext ...&gt;
    &lt;propertyPlaceholder id=&quot;properties&quot; location=&quot;com/mycompany/myprop.properties&quot;/&gt;
 &lt;/camelContext&gt;
 ]]></script>
-</div></div>
-
-    <div class="aui-message success shadowed information-macro">
+</div></div>    <div class="aui-message success shadowed information-macro">
                     <p class="title">Specifying the cache option inside XML</p>
                             <span class="aui-icon icon-success">Icon</span>
                 <div class="message-content">
-                            
-<p>Camel 2.10 onwards supports specifying a value for the cache option both inside the Spring as well as the Blueprint XML.</p>
+                            <p>Camel 2.10 onwards supports specifying a value for the cache option both inside the Spring as well as the Blueprint XML.</p>
                     </div>
     </div>
-
-
-<h3 id="BookInOnePage-UsingaPropertiesfromthe">Using a Properties from the <a shape="rect" href="registry.html">Registry</a></h3>
-<p><strong>Available as of Camel 2.4</strong><br clear="none">
-For example in OSGi you may want to expose a service which returns the properties as a <code>java.util.Properties</code> object.</p>
-
-<p>Then you could setup the <a shape="rect" href="properties.html">Properties</a> component as follows:</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;propertyPlaceholder id=&quot;properties&quot; location=&quot;ref:myProperties&quot;/&gt;
+<h3 id="BookInOnePage-UsingaPropertiesfromthe">Using a Properties from the <a shape="rect" href="registry.html">Registry</a></h3><p><strong>Available as of Camel 2.4</strong><br clear="none"> For example in OSGi you may want to expose a service which returns the properties as a <code>java.util.Properties</code> object.</p><p>Then you could setup the <a shape="rect" href="properties.html">Properties</a> component as follows:</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;propertyPlaceholder id=&quot;properties&quot; location=&quot;ref:myProperties&quot;/&gt;
 ]]></script>
-</div></div>
-<p>Where <code>myProperties</code> is the id to use for lookup in the OSGi registry. Notice we use the <code>ref:</code> prefix to tell Camel that it should lookup the properties for the <a shape="rect" href="registry.html">Registry</a>.</p>
-
-<h3 id="BookInOnePage-Examplesusingpropertiescomponent">Examples using properties component</h3>
-<p>When using property placeholders in the endpoint URIs you can either use the <code>properties:</code> component or define the placeholders directly in the URI. We will show example of both cases, starting with the former.</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[
-// properties
+</div></div><p>Where <code>myProperties</code> is the id to use for lookup in the OSGi registry. Notice we use the <code>ref:</code> prefix to tell Camel that it should lookup the properties for the <a shape="rect" href="registry.html">Registry</a>.</p><h3 id="BookInOnePage-Examplesusingpropertiescomponent">Examples using properties component</h3><p>When using property placeholders in the endpoint URIs you can either use the <code>properties:</code> component or define the placeholders directly in the URI. We will show example of both cases, starting with the former.</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[// properties
 cool.end=mock:result
 
 // route
 from(&quot;direct:start&quot;).to(&quot;properties:{{cool.end}}&quot;);
 ]]></script>
-</div></div>
-
-<p>You can also use placeholders as a part of the endpoint uri:</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[
-// properties
+</div></div><p>You can also use placeholders as a part of the endpoint uri:</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[// properties
 cool.foo=result
 
 // route
 from(&quot;direct:start&quot;).to(&quot;properties:mock:{{cool.foo}}&quot;);
 ]]></script>
-</div></div>
-<p>In the example above the to endpoint will be resolved to <code>mock:result</code>.</p>
-
-<p>You can also have properties with refer to each other such as:</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[
-// properties
+</div></div><p>In the example above the to endpoint will be resolved to <code>mock:result</code>.</p><p>You can also have properties with refer to each other such as:</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[// properties
 cool.foo=result
 cool.concat=mock:{{cool.foo}}
 
 // route
 from(&quot;direct:start&quot;).to(&quot;properties:mock:{{cool.concat}}&quot;);
 ]]></script>
-</div></div>
-<p>Notice how <code>cool.concat</code> refer to another property.</p>
-
-<p>The <code>properties:</code> component also offers you to override and provide a location in the given uri using the <code>locations</code> option:</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;properties:bar.end?locations=com/mycompany/bar.properties&quot;);
+</div></div><p>Notice how <code>cool.concat</code> refer to another property.</p><p>The <code>properties:</code> component also offers you to override and provide a location in the given uri using the <code>locations</code> option:</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;properties:bar.end?locations=com/mycompany/bar.properties&quot;);
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-Examples.22">Examples</h3>
-<p>You can also use property placeholders directly in the endpoint uris without having to use <code>properties:</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[
-// properties
+</div></div><h3 id="BookInOnePage-Examples.22">Examples</h3><p>You can also use property placeholders directly in the endpoint uris without having to use <code>properties:</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[// properties
 cool.foo=result
 
 // route
 from(&quot;direct:start&quot;).to(&quot;mock:{{cool.foo}}&quot;);
 ]]></script>
-</div></div>
-
-<p>And you can use them in multiple wherever you want them:</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[
-// properties
+</div></div><p>And you can use them in multiple wherever you want them:</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[// properties
 cool.start=direct:start
 cool.showid=true
 cool.result=result
@@ -29076,46 +29011,26 @@ from(&quot;{{cool.start}}&quot;)
     .to(&quot;log:{{cool.start}}?showBodyType=false&amp;showExchangeId={{cool.showid}}&quot;)
     .to(&quot;mock:{{cool.result}}&quot;);
 ]]></script>
-</div></div>
-
-<p>You can also your property placeholders when using <a shape="rect" href="producertemplate.html">ProducerTemplate</a> for 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[
-template.sendBody(&quot;{{cool.start}}&quot;, &quot;Hello World&quot;);
+</div></div><p>You can also your property placeholders when using <a shape="rect" href="producertemplate.html">ProducerTemplate</a> for 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[template.sendBody(&quot;{{cool.start}}&quot;, &quot;Hello World&quot;);
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-Examplewithlanguage">Example with <a shape="rect" href="simple.html">Simple</a> language</h3>
-<p>The <a shape="rect" href="simple.html">Simple</a> language now also support using property placeholders, for example in the route 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[
-// properties
+</div></div><h3 id="BookInOnePage-Examplewithlanguage">Example with <a shape="rect" href="simple.html">Simple</a> language</h3><p>The <a shape="rect" href="simple.html">Simple</a> language now also support using property placeholders, for example in the route 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[// properties
 cheese.quote=Camel rocks
 
 // route
 from(&quot;direct:start&quot;)
     .transform().simple(&quot;Hi ${body} do you think ${properties:cheese.quote}?&quot;);
 ]]></script>
-</div></div>
-
-<p>You can also specify the location in the <a shape="rect" href="simple.html">Simple</a> language for 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[
-// bar.properties
+</div></div><p>You can also specify the location in the <a shape="rect" href="simple.html">Simple</a> language for 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[// bar.properties
 bar.quote=Beer tastes good
 
 // route
 from(&quot;direct:start&quot;)
     .transform().simple(&quot;Hi ${body}. ${properties:com/mycompany/bar.properties:bar.quote}.&quot;);
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-AdditionalpropertyplaceholdersupportedinSpringXML">Additional property placeholder supported in Spring XML</h3>
-<p>The property placeholders is also supported in many of the Camel Spring XML tags such as <code>&lt;package&gt;, &lt;packageScan&gt;, &lt;contextScan&gt;, &lt;jmxAgent&gt;, &lt;endpoint&gt;, &lt;routeBuilder&gt;, &lt;proxy&gt;</code> and the others.</p>
-
-<p>The example below has property placeholder in the &lt;jmxAgent&gt; tag:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookInOnePage-AdditionalpropertyplaceholdersupportedinSpringXML">Additional property placeholder supported in Spring XML</h3><p>The property placeholders is also supported in many of the Camel Spring XML tags such as <code>&lt;package&gt;, &lt;packageScan&gt;, &lt;contextScan&gt;, &lt;jmxAgent&gt;, &lt;endpoint&gt;, &lt;routeBuilder&gt;, &lt;proxy&gt;</code> and the others.</p><p>The example below has property placeholder in the &lt;jmxAgent&gt; 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;camelContext xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
     &lt;propertyPlaceholder id=&quot;properties&quot; location=&quot;org/apache/camel/spring/jmx.properties&quot;/&gt;
@@ -29133,10 +29048,7 @@ from(&quot;direct:start&quot;)
 
 &lt;/camelContext&gt;
 ]]></script>
-</div></div>
-
-<p>You can also define property placeholders in the various attributes on the &lt;camelContext&gt; tag such as <code>trace</code> as shown here:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>You can also define property placeholders in the various attributes on the &lt;camelContext&gt; tag such as <code>trace</code> as shown here:</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;camelContext trace=&quot;{{foo.trace}}&quot; xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
     &lt;propertyPlaceholder id=&quot;properties&quot; location=&quot;org/apache/camel/spring/processor/myprop.properties&quot;/&gt;
@@ -29152,15 +29064,8 @@ from(&quot;direct:start&quot;)
     &lt;/route&gt;
 &lt;/camelContext&gt;
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-OverridingapropertysettingusingaJVMSystemProperty">Overriding a property setting using a JVM System Property</h3>
-<p><strong>Available as of Camel 2.5</strong><br clear="none">
-It is possible to override a property value at runtime using a JVM System property without the need to restart the application to pick up the change. This may also be accomplished from the command line by creating a JVM System property of the same name as the property it replaces with a new value. An example of this is given 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[
-PropertiesComponent pc = context.getComponent(&quot;properties&quot;, PropertiesComponent.class);
+</div></div><h3 id="BookInOnePage-OverridingapropertysettingusingaJVMSystemProperty">Overriding a property setting using a JVM System Property</h3><p><strong>Available as of Camel 2.5</strong><br clear="none"> It is possible to override a property value at runtime using a JVM System property without the need to restart the application to pick up the change. This may also be accomplished from the command line by creating a JVM System property of the same name as the property it replaces with a new value. An example of this is given 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[PropertiesComponent pc = context.getComponent(&quot;properties&quot;, PropertiesComponent.class);
 pc.setCache(false);
         
 System.setProperty(&quot;cool.end&quot;, &quot;mock:override&quot;);
@@ -29185,24 +29090,13 @@ System.clearProperty(&quot;cool.result&q
         
 assertMockEndpointsSatisfied();
 ]]></script>
-</div></div>  
-
-<h3 id="BookInOnePage-UsingpropertyplaceholdersforanykindofattributeintheXMLDSL">Using property placeholders for any kind of attribute in the XML DSL</h3>
-<p><strong>Available as of Camel 2.7</strong></p>
-
-    <div class="aui-message hint shadowed information-macro">
+</div></div><h3 id="BookInOnePage-UsingpropertyplaceholdersforanykindofattributeintheXMLDSL">Using property placeholders for any kind of attribute in the XML DSL</h3><p><strong>Available as of Camel 2.7</strong></p>    <div class="aui-message hint shadowed information-macro">
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">
-                            
-<p>If you use OSGi Blueprint then this only works from <strong>2.11.1</strong> or <strong>2.10.5</strong> onwards.</p>
+                            <p>If you use OSGi Blueprint then this only works from <strong>2.11.1</strong> or <strong>2.10.5</strong> onwards.</p>
                     </div>
     </div>
-
-
-<p>Previously it was only the <code>xs:string</code> type attributes in the XML DSL that support placeholders. For example often a timeout attribute would be a <code>xs:int</code> type and thus you cannot set a string value as the placeholder key. This is now possible from Camel 2.7 onwards using a special placeholder namespace.</p>
-
-<p>In the example below we use the <code>prop</code> prefix for the namespace <code><a shape="rect" class="external-link" href="http://camel.apache.org/schema/placeholder">http://camel.apache.org/schema/placeholder</a></code> by which we can use the <code>prop</code> prefix in the attributes in the XML DSLs. Notice how we use that in the <a shape="rect" href="multicast.html">Multicast</a> to indicate that the option <code>stopOnException</code> should be the value of the placeholder with the key "stop".</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<p>Previously it was only the <code>xs:string</code> type attributes in the XML DSL that support placeholders. For example often a timeout attribute would be a <code>xs:int</code> type and thus you cannot set a string value as the placeholder key. This is now possible from Camel 2.7 onwards using a special placeholder namespace.</p><p>In the example below we use the <code>prop</code> prefix for the namespace <code><a shape="rect" class="external-link" href="http://camel.apache.org/schema/placeholder">http://camel.apache.org/schema/placeholder</a></code> by which we can use the <code>prop</code> prefix in the attributes in the XML DSLs. Notice how we use that in the <a shape="rect" href="multicast.html">Multicast</a> to indicate that the option <code>stopOnException</code> should be the value of the placeholder with the key "stop".</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;beans xmlns=&quot;http://www.springframework.org/schema/beans&quot;
        xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
@@ -29239,20 +29133,10 @@ assertMockEndpointsSatisfied();
 
 &lt;/beans&gt;
 ]]></script>
-</div></div>
-
-<p>In our properties file we have the value defined as</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[
-stop=true
+</div></div><p>In our properties file we have the value defined as</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[stop=true
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-UsingpropertyplaceholderintheJavaDSL">Using property placeholder in the Java DSL</h3>
-<p><strong>Available as of Camel 2.7</strong></p>
-
-<p>Likewise we have added support for defining placeholders in the Java DSL using the new <code>placeholder</code> DSL as shown in the following equivalent example:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookInOnePage-UsingpropertyplaceholderintheJavaDSL">Using property placeholder in the Java DSL</h3><p><strong>Available as of Camel 2.7</strong></p><p>Likewise we have added support for defining placeholders in the Java DSL using the new <code>placeholder</code> DSL as shown in the following equivalent 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[
 from(&quot;direct:start&quot;)
     // use a property placeholder for the option stopOnException on the Multicast EIP
@@ -29260,14 +29144,7 @@ from(&quot;direct:start&quot;)
     .multicast().placeholder(&quot;stopOnException&quot;, &quot;stop&quot;)
         .to(&quot;mock:a&quot;).throwException(new IllegalAccessException(&quot;Damn&quot;)).to(&quot;mock:b&quot;);
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-UsingBlueprintpropertyplaceholderwithCamelroutes">Using Blueprint property placeholder with Camel routes</h3>
-<p><strong>Available as of Camel 2.7</strong></p>
-
-<p>Camel supports <a shape="rect" href="using-osgi-blueprint-with-camel.html">Blueprint</a> which also offers a property placeholder service. Camel supports convention over configuration, so all you have to do is to define the OSGi Blueprint property placeholder in the XML file as shown below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Using OSGi blueprint property placeholders in Camel routes</b></div><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookInOnePage-UsingBlueprintpropertyplaceholderwithCamelroutes">Using Blueprint property placeholder with Camel routes</h3><p><strong>Available as of Camel 2.7</strong></p><p>Camel supports <a shape="rect" href="using-osgi-blueprint-with-camel.html">Blueprint</a> which also offers a property placeholder service. Camel supports convention over configuration, so all you have to do is to define the OSGi Blueprint property placeholder in the XML file as shown below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Using OSGi blueprint property placeholders in Camel routes</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;blueprint xmlns=&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;
            xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
@@ -29297,24 +29174,14 @@ from(&quot;direct:start&quot;)
 
 &lt;/blueprint&gt;
 ]]></script>
-</div></div>
-
-<p>By default Camel detects and uses OSGi blueprint property placeholder service. You can disable this by setting the attribute <code>useBlueprintPropertyResolver</code> to false on the <code>&lt;camelContext&gt;</code> definition.</p>
-
-    <div class="aui-message hint shadowed information-macro">
+</div></div><p>By default Camel detects and uses OSGi blueprint property placeholder service. You can disable this by setting the attribute <code>useBlueprintPropertyResolver</code> to false on the <code>&lt;camelContext&gt;</code> definition.</p>    <div class="aui-message hint shadowed information-macro">
                     <p class="title">About placeholder syntaxes</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">
-                            
-<p>Notice how we can use the Camel syntax for placeholders {{ }} in the Camel route, which will lookup the value from OSGi blueprint.<br clear="none">
-The blueprint syntax for placeholders is ${ }. So outside the &lt;camelContext&gt; you must use the ${ } syntax. Where as inside &lt;camelContext&gt; you must use {{ }} syntax.<br clear="none">
-OSGi blueprint allows you to configure the syntax, so you can actually align those if you want.</p>
+                            <p>Notice how we can use the Camel syntax for placeholders {{ }} in the Camel route, which will lookup the value from OSGi blueprint.<br clear="none"> The blueprint syntax for placeholders is ${ }. So outside the &lt;camelContext&gt; you must use the ${ } syntax. Where as inside &lt;camelContext&gt; you must use {{ }} syntax.<br clear="none"> OSGi blueprint allows you to configure the syntax, so you can actually align those if you want.</p>
                     </div>
     </div>
-
-
-<p>You can also explicit refer to a specific OSGi blueprint property placeholder by its id. For that you need to use the Camel's &lt;propertyPlaceholder&gt; as shown in the example below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Explicit referring to a OSGi blueprint placeholder in Camel</b></div><div class="codeContent panelContent pdl">
+<p>You can also explicit refer to a specific OSGi blueprint property placeholder by its id. For that you need to use the Camel's &lt;propertyPlaceholder&gt; as shown in the example below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Explicit referring to a OSGi blueprint placeholder in Camel</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;blueprint xmlns=&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;
            xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
@@ -29348,23 +29215,10 @@ OSGi blueprint allows you to configure t
 
 &lt;/blueprint&gt;
 ]]></script>
-</div></div>
-
-<p>Notice how we use the <code>blueprint</code> scheme to refer to the OSGi blueprint placeholder by its id. This allows you to mix and match, for example you can also have additional schemes in the location. For example to load a file from the classpath you can do:</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[
-location=&quot;blueprint:myblueprint.placeholder,classpath:myproperties.properties&quot;
+</div></div><p>Notice how we use the <code>blueprint</code> scheme to refer to the OSGi blueprint placeholder by its id. This allows you to mix and match, for example you can also have additional schemes in the location. For example to load a file from the classpath you can do:</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[location=&quot;blueprint:myblueprint.placeholder,classpath:myproperties.properties&quot;
 ]]></script>
-</div></div>
-
-<p>Each location is separated by comma.</p>
-
-
-<h4 id="BookInOnePage-OverridingBlueprintpropertyplaceholdersoutsideCamelContext">Overriding Blueprint property placeholders outside CamelContext</h4>
-<p><strong>Available as of Camel 2.10.4</strong></p>
-
-<p>When using Blueprint property placeholder in the Blueprint XML file, you can declare the properties directly in the XML file as shown below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Each location is separated by comma.</p><h4 id="BookInOnePage-OverridingBlueprintpropertyplaceholdersoutsideCamelContext">Overriding Blueprint property placeholders outside CamelContext</h4><p><strong>Available as of Camel 2.10.4</strong></p><p>When using Blueprint property placeholder in the Blueprint XML file, you can declare the properties directly in the XML file as shown below:</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;!-- blueprint property placeholders --&gt;
 &lt;cm:property-placeholder persistent-id=&quot;my-placeholders&quot;&gt;
@@ -29389,12 +29243,7 @@ location=&quot;blueprint:myblueprint.pla
 
 &lt;/camelContext&gt;
 ]]></script>
-</div></div>
-
-<p>Notice that we have a &lt;bean&gt; which refers to one of the properties. And in the Camel route we refer to the other using the {{ }} notation.</p>
-
-<p>Now if you want to override these Blueprint properties from an unit test, you can do this as shown below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Notice that we have a &lt;bean&gt; which refers to one of the properties. And in the Camel route we refer to the other using the {{ }} notation.</p><p>Now if you want to override these Blueprint properties from an unit test, you can do this 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[
 @Override
 protected String useOverridePropertiesWithConfigAdmin(Dictionary props) {
@@ -29405,17 +29254,7 @@ protected String useOverridePropertiesWi
     return &quot;my-placeholders&quot;;
 }
 ]]></script>
-</div></div>
-
-<p>To do this we override and implement the <code>useOverridePropertiesWithConfigAdmin</code> method. We can then put the properties we want to override on the given props parameter. And the return value <strong>must</strong> be the persistence-id of the &lt;cm:property-placeholder&gt; tag, which you define in the blueprint XML file.</p>
-
-<h4 id="BookInOnePage-Using.cfgor.propertiesfileforBlueprintpropertyplaceholders">Using .cfg or .properties file for Blueprint property placeholders</h4>
-<p><strong>Available as of Camel 2.10.4</strong></p>
-
-<p>When using Blueprint property placeholder in the Blueprint XML file, you can declare the properties in a .properties or .cfg file. If you use Apache ServieMix / Karaf then this container has a convention that it loads the properties from a file in the etc directory with the naming etc/pid.cfg, where pid is the persistence-id.</p>
-
-<p>For example in the blueprint XML file we have the persistence-id="stuff", which mean it will load the configuration file as etc/stuff.cfg.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>To do this we override and implement the <code>useOverridePropertiesWithConfigAdmin</code> method. We can then put the properties we want to override on the given props parameter. And the return value <strong>must</strong> be the persistence-id of the &lt;cm:property-placeholder&gt; tag, which you define in the blueprint XML file.</p><h4 id="BookInOnePage-Using.cfgor.propertiesfileforBlueprintpropertyplaceholders">Using .cfg or .properties file for Blueprint property placeholders</h4><p><strong>Available as of Camel 2.10.4</strong></p><p>When using Blueprint property placeholder in the Blueprint XML file, you can declare the properties in a .properties or .cfg file. If you use Apache ServieMix / Karaf then this container has a convention that it loads the properties from a file in the etc directory with the naming etc/pid.cfg, where pid is the persistence-id.</p><p>For example in the blueprint XML file we have the persistence-id="stuff", which mean it will load the co
 nfiguration file as etc/stuff.cfg.</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;!-- blueprint property placeholders, that will use etc/stuff.cfg as the properties file --&gt;
 &lt;cm:property-placeholder persistent-id=&quot;stuff&quot;/&gt;
@@ -29435,10 +29274,7 @@ protected String useOverridePropertiesWi
 
 &lt;/camelContext&gt;
 ]]></script>
-</div></div>
-
-<p>Now if you want to unit test this blueprint XML file, then you can override the <code>loadConfigAdminConfigurationFile</code> and tell Camel which file to load as shown below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Now if you want to unit test this blueprint XML file, then you can override the <code>loadConfigAdminConfigurationFile</code> and tell Camel which file to load 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[
 @Override
 protected String[] loadConfigAdminConfigurationFile() {
@@ -29447,24 +29283,11 @@ protected String[] loadConfigAdminConfig
     return new String[]{&quot;src/test/resources/etc/stuff.cfg&quot;, &quot;stuff&quot;};
 }
 ]]></script>
-</div></div>
-
-<p>Notice that this method requires to return a String[] with 2 values. The 1st value is the path for the configuration file to load.<br clear="none">
-The 2nd value is the persistence-id of the &lt;cm:property-placeholder&gt; tag.</p>
-
-<p>The stuff.cfg file is just a plain properties file with the property placeholders such as:</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[
-## this is a comment
+</div></div><p>Notice that this method requires to return a String[] with 2 values. The 1st value is the path for the configuration file to load.<br clear="none"> The 2nd value is the persistence-id of the &lt;cm:property-placeholder&gt; tag.</p><p>The stuff.cfg file is just a plain properties file with the property placeholders such as:</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[## this is a comment
 greeting=Bye
 ]]></script>
-</div></div>
-
-
-<h4 id="BookInOnePage-Using.cfgfileandoverridingpropertiesforBlueprintpropertyplaceholders">Using .cfg file and overriding properties for Blueprint property placeholders</h4>
-
-<p>You can do both as well. Here is a complete example. First we have the Blueprint XML file:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="BookInOnePage-Using.cfgfileandoverridingpropertiesforBlueprintpropertyplaceholders">Using .cfg file and overriding properties for Blueprint property placeholders</h4><p>You can do both as well. Here is a complete example. First we have the Blueprint 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;blueprint xmlns=&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;
            xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
@@ -29496,10 +29319,7 @@ greeting=Bye
 
 &lt;/blueprint&gt;
 ]]></script>
-</div></div>
-
-<p>And in the unit test class we do as follows:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>And in the unit test class we do 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[
 /**
  * This example will load a Blueprint .cfdg file, and also override its property placeholders from this unit test
@@ -29540,25 +29360,12 @@ public class ConfigAdminLoadConfiguratio
 
 }
 ]]></script>
-</div></div>
-
-<p>And the <code>etc/stuff.cfg</code> configuration file contains</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[
-greeting=Bye
+</div></div><p>And the <code>etc/stuff.cfg</code> configuration file contains</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[greeting=Bye
 echo=Yay
 destination=mock:result
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-BridgingSpringandCamelpropertyplaceholders">Bridging Spring and Camel property placeholders</h3>
-<p><strong>Available as of Camel 2.10</strong></p>
-
-<p>The Spring Framework does not allow 3rd party frameworks such as Apache Camel to seamless hook into the Spring property placeholder mechanism. However you can easily bridge Spring and Camel by declaring a Spring bean with the type <code>org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer</code>, which is a Spring <code>org.springframework.beans.factory.config.PropertyPlaceholderConfigurer</code> type. </p>
-
-<p>To bridge Spring and Camel you must define a single bean as shown below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Bridging Spring and Camel property placeholders</b></div><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookInOnePage-BridgingSpringandCamelpropertyplaceholders">Bridging Spring and Camel property placeholders</h3><p><strong>Available as of Camel 2.10</strong></p><p>The Spring Framework does not allow 3rd party frameworks such as Apache Camel to seamless hook into the Spring property placeholder mechanism. However you can easily bridge Spring and Camel by declaring a Spring bean with the type <code>org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer</code>, which is a Spring <code>org.springframework.beans.factory.config.PropertyPlaceholderConfigurer</code> type.</p><p>To bridge Spring and Camel you must define a single bean as shown below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Bridging Spring and Camel property placeholders</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 
 &lt;!-- bridge spring property placeholder with Camel --&gt;
@@ -29568,12 +29375,7 @@ destination=mock:result
 &lt;/bean&gt;
 
 ]]></script>
-</div></div>
-
-<p>You <strong>must not</strong> use the spring &lt;context:property-placeholder&gt; namespace at the same time; this is not possible.</p>
-
-<p>After declaring this bean, you can define property placeholders using both the Spring style, and the Camel style within the &lt;camelContext&gt; tag as shown below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Using bridge property placeholders</b></div><div class="codeContent panelContent pdl">
+</div></div><p>You <strong>must not</strong> use the spring &lt;context:property-placeholder&gt; namespace at the same time; this is not possible.</p><p>After declaring this bean, you can define property placeholders using both the Spring style, and the Camel style within the &lt;camelContext&gt; tag as shown below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Using bridge property placeholders</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 
 &lt;!-- a bean that uses Spring property placeholder --&gt;
@@ -29592,41 +29394,17 @@ destination=mock:result
 &lt;/camelContext&gt;
 
 ]]></script>
-</div></div>
-
-<p>Notice how the hello bean is using pure Spring property placeholders using the ${ } notation. And in the Camel routes we use the Camel placeholder notation with {{ }}.</p>
-
-<h4 id="BookInOnePage-ClashingSpringpropertyplaceholderswithCamelslanguage">Clashing Spring property placeholders with Camels <a shape="rect" href="simple.html">Simple</a> language</h4>
-<p>Take notice when using Spring bridging placeholder then the spring ${ } syntax clashes with the <a shape="rect" href="simple.html">Simple</a> in Camel, and therefore take care. For 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[
-&lt;setHeader headerName=&quot;Exchange.FILE_NAME&quot;&gt;
+</div></div><p>Notice how the hello bean is using pure Spring property placeholders using the ${ } notation. And in the Camel routes we use the Camel placeholder notation with {{ }}.</p><h4 id="BookInOnePage-ClashingSpringpropertyplaceholderswithCamelslanguage">Clashing Spring property placeholders with Camels <a shape="rect" href="simple.html">Simple</a> language</h4><p>Take notice when using Spring bridging placeholder then the spring ${ } syntax clashes with the <a shape="rect" href="simple.html">Simple</a> in Camel, and therefore take care. For 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[&lt;setHeader headerName=&quot;Exchange.FILE_NAME&quot;&gt;
   &lt;simple&gt;{{file.rootdir}}/${in.header.CamelFileName}&lt;/simple&gt;
 &lt;/setHeader&gt;
 ]]></script>
-</div></div>
-<p>clashes with Spring property placeholders, and you should use $simple{ } to indicate using the <a shape="rect" href="simple.html">Simple</a> language in Camel.</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[
-&lt;setHeader headerName=&quot;Exchange.FILE_NAME&quot;&gt;
+</div></div><p>clashes with Spring property placeholders, and you should use $simple{ } to indicate using the <a shape="rect" href="simple.html">Simple</a> language in Camel.</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[&lt;setHeader headerName=&quot;Exchange.FILE_NAME&quot;&gt;
   &lt;simple&gt;{{file.rootdir}}/$simple{in.header.CamelFileName}&lt;/simple&gt;
 &lt;/setHeader&gt;
 ]]></script>
-</div></div>
-
-<p>An alternative is to configure the <code>PropertyPlaceholderConfigurer</code> with <code>ignoreUnresolvablePlaceholders</code> option to <code>true</code>.</p>
-
-
-<h3 id="BookInOnePage-OverridingpropertiesfromCameltestkit">Overriding properties from Camel test kit</h3>
-<p><strong>Available as of Camel 2.10</strong></p>
-
-<p>When <a shape="rect" href="testing.html">Testing</a> with Camel and using the <a shape="rect" href="properties.html">Properties</a> component, you may want to be able to provide the properties to be used from directly within the unit test source code.<br clear="none">
-This is now possible from Camel 2.10 onwards, as the Camel test kits, eg <code>CamelTestSupport</code> class offers the following methods</p>
-<ul class="alternate"><li>useOverridePropertiesWithPropertiesComponent</li><li>ignoreMissingLocationWithPropertiesComponent</li></ul>
-
-
-<p>So for example in your unit test classes, you can override the <code>useOverridePropertiesWithPropertiesComponent</code> method and return a <code>java.util.Properties</code> that contains the properties which should be preferred to be used.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Providing properties from within unit test source</b></div><div class="codeContent panelContent pdl">
+</div></div><p>An alternative is to configure the <code>PropertyPlaceholderConfigurer</code> with <code>ignoreUnresolvablePlaceholders</code> option to <code>true</code>.</p><h3 id="BookInOnePage-OverridingpropertiesfromCameltestkit">Overriding properties from Camel test kit</h3><p><strong>Available as of Camel 2.10</strong></p><p>When <a shape="rect" href="testing.html">Testing</a> with Camel and using the <a shape="rect" href="properties.html">Properties</a> component, you may want to be able to provide the properties to be used from directly within the unit test source code.<br clear="none"> This is now possible from Camel 2.10 onwards, as the Camel test kits, eg <code>CamelTestSupport</code> class offers the following methods</p><ul class="alternate"><li>useOverridePropertiesWithPropertiesComponent</li><li>ignoreMissingLocationWithPropertiesComponent</li></ul><p>So for example in your unit test classes, you can override the <code>useOverridePropertiesWithPropertiesComponent</cod
 e> method and return a <code>java.util.Properties</code> that contains the properties which should be preferred to be used.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Providing properties from within unit test source</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 // override this method to provide our custom properties we use in this unit test
 @Override
@@ -29637,22 +29415,8 @@ protected Properties useOverrideProperti
     return extra;
 }
 ]]></script>
-</div></div>
-
-<p>This can be done from any of the Camel Test kits, such as camel-test, camel-test-spring, and camel-test-blueprint.</p>
-
-<p>The <code>ignoreMissingLocationWithPropertiesComponent</code> can be used to instruct Camel to ignore any locations which was not discoverable, for example if you run the unit test, in an environment that does not have access to the location of the properties. </p>
-
-
-<h3 id="BookInOnePage-Using@PropertyInject">Using @PropertyInject</h3>
-<p><strong>Available as of Camel 2.12</strong></p>
-
-<p>Camel allows to inject property placeholders in POJOs using the @PropertyInject annotation which can be set on fields and setter methods.<br clear="none">
-For example you can use that with <code>RouteBuilder</code> classes, such 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[
-public class MyRouteBuilder extends RouteBuilder {
+</div></div><p>This can be done from any of the Camel Test kits, such as camel-test, camel-test-spring, and camel-test-blueprint.</p><p>The <code>ignoreMissingLocationWithPropertiesComponent</code> can be used to instruct Camel to ignore any locations which was not discoverable, for example if you run the unit test, in an environment that does not have access to the location of the properties.</p><h3 id="BookInOnePage-Using@PropertyInject">Using @PropertyInject</h3><p><strong>Available as of Camel 2.12</strong></p><p>Camel allows to inject property placeholders in POJOs using the @PropertyInject annotation which can be set on fields and setter methods.<br clear="none"> For example you can use that with <code>RouteBuilder</code> classes, such 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[public class MyRouteBuilder extends RouteBuilder {
 
     @PropertyInject(&quot;hello&quot;)
     private String greeting;
@@ -29666,31 +29430,15 @@ public class MyRouteBuilder extends Rout
 
 }
 ]]></script>
-</div></div>
-
-<p>Notice we have annotated the greeting field with @PropertyInject and define it to use the key "hello". Camel will then lookup the property with this key and inject its value, converted to a String type.</p>
-
-<p>You can also use multiple placeholders and text in the key, for example we can do:</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[
-    @PropertyInject(&quot;Hello {{name}} how are you?&quot;)
+</div></div><p>Notice we have annotated the greeting field with @PropertyInject and define it to use the key "hello". Camel will then lookup the property with this key and inject its value, converted to a String type.</p><p>You can also use multiple placeholders and text in the key, for example we can do:</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[    @PropertyInject(&quot;Hello {{name}} how are you?&quot;)
     private String greeting;
 ]]></script>
-</div></div>
-
-<p>This will lookup the placeholder with they key "name".</p>
-
-<p>You can also add a default value if the key does not exists, such as:</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[
-    @PropertyInject(value = &quot;myTimeout&quot;, defaultValue = &quot;5000&quot;)
+</div></div><p>This will lookup the placeholder with they key "name".</p><p>You can also add a default value if the key does not exists, such as:</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[    @PropertyInject(value = &quot;myTimeout&quot;, defaultValue = &quot;5000&quot;)
     private int timeout;
 ]]></script>
-</div></div>
-
-
-<h2 id="BookInOnePage-SeeAlso.69">See Also</h2>
-<ul class="alternate"><li><a shape="rect" href="properties.html">Properties</a> component</li></ul>
+</div></div><h2 id="BookInOnePage-SeeAlso.69">See Also</h2><ul class="alternate"><li><a shape="rect" href="properties.html">Properties</a> component</li></ul>
 
 <h3 id="BookInOnePage-SeeAlso.70">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>
@@ -29786,7 +29534,7 @@ ref:someName[?options]
 </div></div><p>Format of restletUrl:</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[protocol://hostname[:port][/resourcePattern]
 ]]></script>

[... 6 lines stripped ...]
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.



Mime
View raw message