camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r938718 - in /websites/production/camel/content: cache/main.pageCache camel-2150-release.html how-do-i-configure-endpoints.html
Date Mon, 02 Feb 2015 21:18:23 GMT
Author: buildbot
Date: Mon Feb  2 21:18:22 2015
New Revision: 938718

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-2150-release.html
    websites/production/camel/content/how-do-i-configure-endpoints.html

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

Modified: websites/production/camel/content/camel-2150-release.html
==============================================================================
--- websites/production/camel/content/camel-2150-release.html (original)
+++ websites/production/camel/content/camel-2150-release.html Mon Feb  2 21:18:22 2015
@@ -84,7 +84,7 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h1 id="Camel2.15.0Release-Camel2.15.0release(currentlyinprogress)">Camel&#160;2.15.0 release (currently in progress)</h1><div style="padding-right:20px;float:left;margin-left:-20px;"><p><img class="confluence-embedded-image confluence-external-resource" src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png" data-image-src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png"></p></div><div style="min-height:200px">&#160;</div><h2 id="Camel2.15.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to the 2.15.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)</p><ul><li><span>Component, data format, language and eip documentation now included in the built component JARs. And Java API and JMX API to access that documentation. And APIs to explain an endpoint uri, eip configuration and what all those configured options mean. In other words the same level of complete d
 ocumentation of your Camel apps at both design and runtime, accessible from Java / JMX and tooling.</span></li><li><span>Component, data format, language and eip can now have&#160;associated&#160;label(s) which are used for grouping components into: core, database, messaging, http, rest, etc.</span></li><li><span>Provide Configurer for user to configure the CXF conduit and CXF destination from Java code</span></li><li><span><span>Added a <code>DelegateEndpoint</code>&#160;interface into Camel API</span></span></li><li>Support to setup the SslContextParameters in the <a shape="rect" href="restlet.html">camel-restlet</a> component</li><li>Java DSL - Should support nested choice in doTry .. doCatch</li><li><a shape="rect" href="mongodb.html">MongoDb</a> component now <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-7996">stores OIDs</a>&#160;of the inserted records in the message header</li><li><a shape="rect" href="recipient-list.html">Recipient 
 List</a> now supports specifying custom&#160;<a shape="rect" href="exchange-pattern.html">Exchange Pattern</a> in the endpoint ur's</li><li><a shape="rect" href="type-converter.html">Type Converter</a> to enum's is now case insensitive, so you can convert safely level=info to an enum with name Level.INFO etc.</li><li><a shape="rect" href="xslt.html">XSLT</a> and&#160;<a shape="rect" href="https://cwiki.apache.org/confluence/display/SM/Validation">Validation</a> components now provides all their endpoint configurations in the endpoint, and not only in the component, making these components like any other components.</li><li>Made the <a shape="rect" href="karaf.html">Camel Karaf Commands</a> reusable by moving common code into a&#160;<code>camel-commands-core</code> module that SPI can extend and plugin Camel commands for other environments.</li><li>Further hardening of the&#160;<a shape="rect" href="sjms.html">SJMS</a>&#160;component.</li><li><a shape="rect" href="rest-dsl.html">Rest
  DSL</a> with embedded routes now supports <a shape="rect" href="exception-clause.html">onException</a>, <a shape="rect" href="intercept.html">intercept</a> etc in use for those embedded routes, just like any regular routes.&#160;</li><li><a shape="rect" href="rest-dsl.html">Rest DSL</a> now by default uses custom error message as-is without attempting to binding output (requires a HTTP error code of 300+ is set as a header)</li><li>Camel&#160;<a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a> now supports specifying a default value together with the key to lookup.</li><li>Camel&#160;<a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a> now supports not having to define a PropertiesComponent if all the placeholder keys has default values which are to be used (less configuration needed in those situations).</li><li>Camel&#160;<a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a> now supports 
 3rd party functions to lookup the property values, this allow end users to implement their own logic - we provide 3 out of the box functions to lookup values from OS environment variable, JVM system properties, or the service name idiom.</li><li><a shape="rect" href="rabbitmq.html">RabbitMQ</a> now pools Channels for the producer to avoid sharing same Channel among concurrent producers which are not recommended by RabbitMQ client.</li><li>Camel commands is now reusable outside Apache Karaf as a base by the&#160;<code>commands-core</code> module.</li><li>Camel commands using <a shape="rect" class="external-link" href="http://www.jolokia.org/" rel="nofollow">Jolokia</a> for remote communication by the&#160;<code>commands-jolokia</code> module.</li><li>More minor processors such as setHeader, removeHeader, removeHeaders and ditto for properties is now also enlisted in JMX under processors.</li><li>Optimized usage of type conversion during routing reducing the number of attempts needed.
 </li><li>Optimized CaseInsentiveMap used as message headers to use a single map instead of two and yield less memory overhead and performance</li><li>Asynchronous routing engine that are forced to block threads now exposes this using a <a shape="rect" href="asyncprocessorawaitmanager.html">manager</a> that offers runtime insight using JMX. And as well attempts to free blocked threads during graceful shutdown, to avoid any threads hanging in the JVM.</li><li><a shape="rect" href="swagger.html">Swagger</a> now supports any kind of runtime environment, as only JMX being enabled is required.</li><li><a shape="rect" href="xml-security-component.html">XML Security component</a> supports now&#160;&#160;XAdES-BES/EPES&#160;in the signer endpoint.</li><li><a shape="rect" href="hl7.html">HL7</a> MLLP codec now supports&#160;<a shape="rect" href="netty4.html">Netty4</a> based transport.</li><li>Inflight repository now allows to browse the current inflight exchanges to obtain information where 
 these exchanges are inflight and for how long. Expose this information in JMX and Camel commands as well.</li><li><a shape="rect" href="graceful-shutdown.html">Graceful Shutdown</a> now logs information about the inflight exchanges that are still present during shutdown and a timeout was hit.</li><li><a shape="rect" href="message-history.html">Message History</a> which dumps&#160;Exchange information not supports the&#160;<span style="color: rgb(0,0,0);"><a shape="rect" href="how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.html">Exchange.LOG_DEBUG_BODY_MAX_CHARS</a> option to limit the max chars outputted in the logs.</span></li><li><code>DefaultClassLoader</code> now fallback and use the application context classloader that may have been set on&#160;<code>CamelContext</code> to better be able to load classes/resources from classpath in different runtime environments.<span style="color: rgb(0,0,0);"><br clear="none"></span></li><li><a shape="rect" href="camel-jmx.htm
 l">Camel JMX</a> now includes current inflight exchanges at processor level, which means we can have a complete breakdown where exchanges are, and as well from the improved&#160;<code>InflightRegistry</code> which has APi and JMX api to browse the current inflight with details of the exchange and processing times etc.</li><li>Support for Jetty 9 using the new&#160;<code>camel-component-jetty9</code> module.</li><li>The&#160;<code>EndpointRegistry</code> now stores endpoints in two caches; a static unbounded cache to keep endpoints for their lifetime, and a dynamic limited cache to keep only the recently used endpoints.&#160;</li><li><a shape="rect" href="endpoint.html">Endpoint</a>'s used by routes are kept in the static cache of the&#160;<code>EndpointRegistry</code> as long as the lifetime of the routes.</li><li>Removing a route now also remove its static&#160;<a shape="rect" href="endpoint.html">Endpoint</a>'s from the&#160;<code>EndpointRegistry</code> (if those endpoints are no
 t shared and used by other routes). Mind that any dynamic endpoint created during routing from dynamic&#160;<a shape="rect" href="eip.html">EIP</a>s such as recipient list, routing slip, dynamic router etc, are not removed from the <code>EndpointRegistry</code>&#160;when the route is removed.</li><li><a shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a> now logs a WARN if a new exception occurred while it was attempting to process the dead letter message. The new exception will by default be handled so the&#160;<a shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a> always complete succesfull. The new option&#160;<span>deadLetterHandleNewException</span><span>&#160;can be set to&#160;<code>false</code> to turn this off.</span></li><li><span><a shape="rect" href="groovy.html">GroovyShell</a> creation process can now be <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-8259">customized</a> using <code>GroovyShellF
 actory</code> SPI interface.</span></li></ul><h3 id="Camel2.15.0Release-Fixedissues">Fixed issues</h3><ul><li>Fixed processors was not enlisted in JMX when routes was transacted.</li><li>Fixed the NullPointerException when using CXF endpoint with enrich</li><li>Fixed the&#160;endpointProperty of&#160;restConfiguration doesn't work issue</li><li>Fixed the issue that&#160;CircuitBreakerLoadBalancer fails on async processors</li><li>Fixed&#160;MyBatis consumer <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-8011">ignoring maxMessagesPerPoll</a> option</li><li>Fixed potential issue with&#160;pollEnrich not triggering error handler if an exception was thrown in the polling.</li><li>Fixed a memory leak if using&#160;<a shape="rect" href="dynamic-router.html">Dynamic Router</a> that loops many times, and uses&#160;any of&#160;<code>convertBodyTo</code> or&#160;<code>setBody</code> or&#160;<code>transform</code> in the loop, causing memory to stack up
  until the Exchange is done.</li><li>Fixed and improved how&#160;<a shape="rect" href="bean.html">Bean</a>&#160;component and&#160;<a shape="rect" href="simple.html">Simple</a>&#160;language invoking beans detect methods that are overridden, and able to filter and apply this as a single method, to be invoked. Avoids AmbiguousMethodCallException&#160;being thrown.</li><li>Fixed a thread leak if restarting routes using stop/start and the routes is a scheduled poll consumer, such as file/ftp&#160;components.</li><li>Using ?exchangePattern=InOnly or InOut in endpoint uris now take precedence as the pattern in use when sending to the endpoint, using to/recipient list.</li><li><a shape="rect" href="mail.html">Mail</a>&#160;component no longer includes headers starting with&#160;<code>Camel</code> in their keys, as those are consider internal headers and should not be included in the sent emails.<br clear="none"><br clear="none"></li></ul><h3 id="Camel2.15.0Release-New">New <a shape="rect"
  href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a></h3><h3 id="Camel2.15.0Release-New.1">New <a shape="rect" href="components.html">Components</a></h3><ul><li><a shape="rect" href="beanstalk.html">camel-beanstalk</a> - for working with Amazon Beanstalk jobs.</li><li>came-cassandraql -&#160;Cassandra CQL3 support</li><li><code>camel-chunk</code> - for templating with Chunk engine.</li><li><a shape="rect" href="docker.html">camel-docker</a> - to communicate with Docker.</li><li>camel-github - for integrating with github</li><li>camel-google-calendar -&#160;provides access to&#160;<a shape="rect" class="external-link" href="http://google.com/calendar" rel="nofollow">Google Calendar</a>&#160;via the&#160;<a shape="rect" class="external-link" href="https://developers.google.com/google-apps/calendar/v3/reference/" rel="nofollow">Google Calendar Web APIs</a>.</li><li>camel-google-mail -&#160;provides access to&#160;<a shape="rect" class="external-link" href="h
 ttp://gmail.com/" rel="nofollow">Gmail</a>&#160;via the&#160;<a shape="rect" class="external-link" href="https://developers.google.com/gmail/api/v1/reference/" rel="nofollow">Google Mail Web APIs</a>.</li><li><a shape="rect" href="hipchat.html">camel-hipchat</a> - to integrate with the Hipchat service</li><li>camel-pgevent -&#160;Component for sending/receiving notifications in PostgreSQL via the pgjdbc-ng driver</li><li>camel-jira - for integrating with JIRA issue tracker</li><li>camel-scr - for using Camel with <a shape="rect" class="external-link" href="http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html">SCR</a>&#160;(OSGi declarative services) on OSGi containers such as Apache Karaf</li><li><a shape="rect" href="spring-boot.html">camel-spring-boot</a> - for using Camel with Spring Boot</li><li>camel-test-spring40 - for testing with Spring 4.0.x. camel-test-spring is for Spring 4.1.x onwards.</li></ul><h3 id="Camel2.15.0Release-Ne
 wDSL">New DSL</h3><ul><li>Added <strong>removeProperties</strong> to remove the properties from exchange.</li></ul><h3 id="Camel2.15.0Release-NewAnnotations">New Annotations</h3><h3 id="Camel2.15.0Release-NewDataFormats">New <a shape="rect" href="data-format.html">Data Formats</a></h3><ul><li>camel-univocity-parsers</li></ul><h3 id="Camel2.15.0Release-New.2">New <a shape="rect" href="languages.html">Languages</a></h3><h3 id="Camel2.15.0Release-New.3">New <a shape="rect" href="examples.html">Examples</a></h3><h3 id="Camel2.15.0Release-New.4">New <a shape="rect" href="tutorials.html">Tutorials</a></h3><h2 id="Camel2.15.0Release-KnownIssues">Known Issues</h2><h2 id="Camel2.15.0Release-DependencyUpgrades"><span>Dependency Upgrades</span></h2><ul><li>AWS-Java-SDK 1.8.3 to 1.8.9.1</li><li>Codahale Metrics 3.0 to 3.1</li><li>CXF 3.0.2 to 3.0.3</li><li>Hazelcast 3.3.2 to 3.4</li><li>JAXB 2.2.7 to 2.2.11</li><li>JRuby 1.7.16 to 1.7.18</li><li>Guava 17.0 to 18.0</li><li>Jsch 0.1.50 to 0.1.51<
 /li><li>JsonPath 1.1.0 to 1.2.0</li><li>Spring 4.0.7.RELEASE to 4.1.4.RELEASE</li><li>Spring Security 3.1.7.RELEASE to 3.2.5.RELEASE</li><li>RX Java 0.20 to 1.0.4</li><li>... and many other upgrades</li></ul><h2 id="Camel2.15.0Release-Importantchangestoconsiderwhenupgrading">Important changes to consider when upgrading</h2><ul><li>Spring 4.1.x is now the default out of the box Spring version.</li><li><span style="color: rgb(0,0,0);">Unit testing with Spring 4.0.x requires using camel-test-spring40, as camel-test-spring is for Spring 4.1 or better.</span></li><li><span style="color: rgb(0,0,0);">Remember to add&#160;<code class="java color1">@BootstrapWith</code><code class="java plain">(CamelTestContextBootstrapper.</code><code class="java keyword">class</code><code class="java plain">)</code>&#160;if upgrading from Spring 3.x or 4.0.x to Spring 4.1 onwards, and using the camel-test-spring module.</span></li><li><a shape="rect" href="xslt.html">XSLT</a>&#160;component now require co
 nfiguring&#160;<code>transformerFactory</code> using&#160;<a shape="rect" href="uris.html">URIs</a> with the #syntax to refer to a bean. Just like any other component would do.</li><li>Slight refactor in&#160;<code>camel-metrics</code> component which may affect users who are using the java endpoint types instead of configuring using uris</li><li><code>camel-csv</code> upgraded to Commons CSV 1.x which has a different API than the old 0.x version. End users may need to adjust their code.</li><li><code>camel-sjms</code> has been refactored a bit to further harden this component.&#160;End users may need to adjust their code.</li><li>The <a shape="rect" href="simple.html">simple</a> function properties:locations:key has been renamed to properties-location:locations:key, as it would clash with the new functionality to specify a default value after the key name, eg properties:key:default</li><li>Removed the backlog tracer commands from the Karaf Camel commands as they are not suitable fo
 r a CLI environment</li><li>The need for runtime specific servlets in <a shape="rect" href="swagger.html">Swagger</a>&#160;has been removed, and instead just use the default servlet which is provided out of the box.&#160;</li><li><code>org.apache.camel.spi.InflightRepository</code> now includes additional methods for browsing in-flight exchanges.</li><li>Using ?exchangePattern=InOnly or InOut in endpoint uris now take precedence as the pattern in use when sending to the endpoint, using to/recipient list.</li><li><code>DefaultClassLoader</code> now fallback and use the application context classloader that may have been set on&#160;<code>CamelContext</code> to better be able to load classes/resources from classpath in different runtime environments.</li><li><a shape="rect" href="mail.html">Mail</a>&#160;component no longer includes headers starting with&#160;<code>Camel</code> in their keys, as those are consider internal headers and should not be included in the sent emails.</li><li>
 Removing a route now also remove its static&#160;<a shape="rect" href="endpoint.html">Endpoint</a>'s from the&#160;<code>EndpointRegistry</code> (if those endpoints are not shared and used by other routes). Mind that any dynamic endpoint created during routing from dynamic&#160;<a shape="rect" href="eip.html">EIP</a>s such as recipient list, routing slip, dynamic router etc, are not removed from the <code>EndpointRegistry</code>&#160;when the route is removed.</li><li>All boolean isFoo methods on the model classes has been removed to ensure the model has consistent java bean getter/setter style with exactly one getter and one setter of the same type.<br clear="none"><br clear="none"></li></ul><h2 id="Camel2.15.0Release-GettingtheDistributions">Getting the Distributions</h2><h3 id="Camel2.15.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><t
 h 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.15.0/apache-camel-x.y.x.zip">apache-camel-2.15.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.15.0/apache-camel-x.y.x.zip.asc">apache-camel-2.15.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.15.0/apache-camel-x.y.x.tar.gz">apache-camel-2.15.0.ta
 r.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.15.0/apache-camel-x.y.x.tar.gz.asc">apache-camel-2.15.0.tar.gz.asc</a></p></td></tr></tbody></table></div>    <div class="aui-message hint shadowed information-macro">
+<div class="wiki-content maincontent"><h1 id="Camel2.15.0Release-Camel2.15.0release(currentlyinprogress)">Camel&#160;2.15.0 release (currently in progress)</h1><div style="padding-right:20px;float:left;margin-left:-20px;"><p><img class="confluence-embedded-image confluence-external-resource" src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png" data-image-src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png"></p></div><div style="min-height:200px">&#160;</div><h2 id="Camel2.15.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to the 2.15.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)</p><ul><li><span>Component, data format, language and eip documentation now included in the built component JARs. And Java API and JMX API to access that documentation. And APIs to explain an endpoint uri, eip configuration and what all those configured options mean. In other words the same level of complete d
 ocumentation of your Camel apps at both design and runtime, accessible from Java / JMX and tooling.</span></li><li><span>Component, data format, language and eip can now have&#160;associated&#160;label(s) which are used for grouping components into: core, database, messaging, http, rest, etc.</span></li><li><span>Provide Configurer for user to configure the CXF conduit and CXF destination from Java code</span></li><li><span><span>Added a <code>DelegateEndpoint</code>&#160;interface into Camel API</span></span></li><li>Support to setup the SslContextParameters in the <a shape="rect" href="restlet.html">camel-restlet</a> component</li><li>Java DSL - Should support nested choice in doTry .. doCatch</li><li><a shape="rect" href="mongodb.html">MongoDb</a> component now <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-7996">stores OIDs</a>&#160;of the inserted records in the message header</li><li><a shape="rect" href="recipient-list.html">Recipient 
 List</a> now supports specifying custom&#160;<a shape="rect" href="exchange-pattern.html">Exchange Pattern</a> in the endpoint ur's</li><li><a shape="rect" href="type-converter.html">Type Converter</a> to enum's is now case insensitive, so you can convert safely level=info to an enum with name Level.INFO etc.</li><li><a shape="rect" href="xslt.html">XSLT</a> and&#160;<a shape="rect" href="https://cwiki.apache.org/confluence/display/SM/Validation">Validation</a> components now provides all their endpoint configurations in the endpoint, and not only in the component, making these components like any other components.</li><li>Made the <a shape="rect" href="karaf.html">Camel Karaf Commands</a> reusable by moving common code into a&#160;<code>camel-commands-core</code> module that SPI can extend and plugin Camel commands for other environments.</li><li>Further hardening of the&#160;<a shape="rect" href="sjms.html">SJMS</a>&#160;component.</li><li><a shape="rect" href="rest-dsl.html">Rest
  DSL</a> with embedded routes now supports <a shape="rect" href="exception-clause.html">onException</a>, <a shape="rect" href="intercept.html">intercept</a> etc in use for those embedded routes, just like any regular routes.&#160;</li><li><a shape="rect" href="rest-dsl.html">Rest DSL</a> now by default uses custom error message as-is without attempting to binding output (requires a HTTP error code of 300+ is set as a header)</li><li>Camel&#160;<a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a> now supports specifying a default value together with the key to lookup.</li><li>Camel&#160;<a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a> now supports not having to define a PropertiesComponent if all the placeholder keys has default values which are to be used (less configuration needed in those situations).</li><li>Camel&#160;<a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a> now supports 
 3rd party functions to lookup the property values, this allow end users to implement their own logic - we provide 3 out of the box functions to lookup values from OS environment variable, JVM system properties, or the service name idiom.</li><li><a shape="rect" href="rabbitmq.html">RabbitMQ</a> now pools Channels for the producer to avoid sharing same Channel among concurrent producers which are not recommended by RabbitMQ client.</li><li>Camel commands is now reusable outside Apache Karaf as a base by the&#160;<code>commands-core</code> module.</li><li>Camel commands using <a shape="rect" class="external-link" href="http://www.jolokia.org/" rel="nofollow">Jolokia</a> for remote communication by the&#160;<code>commands-jolokia</code> module.</li><li>More minor processors such as setHeader, removeHeader, removeHeaders and ditto for properties is now also enlisted in JMX under processors.</li><li>Optimized usage of type conversion during routing reducing the number of attempts needed.
 </li><li>Optimized CaseInsentiveMap used as message headers to use a single map instead of two and yield less memory overhead and performance</li><li>Asynchronous routing engine that are forced to block threads now exposes this using a <a shape="rect" href="asyncprocessorawaitmanager.html">manager</a> that offers runtime insight using JMX. And as well attempts to free blocked threads during graceful shutdown, to avoid any threads hanging in the JVM.</li><li><a shape="rect" href="swagger.html">Swagger</a> now supports any kind of runtime environment, as only JMX being enabled is required.</li><li><a shape="rect" href="xml-security-component.html">XML Security component</a> supports now&#160;&#160;XAdES-BES/EPES&#160;in the signer endpoint.</li><li><a shape="rect" href="hl7.html">HL7</a> MLLP codec now supports&#160;<a shape="rect" href="netty4.html">Netty4</a> based transport.</li><li>Inflight repository now allows to browse the current inflight exchanges to obtain information where 
 these exchanges are inflight and for how long. Expose this information in JMX and Camel commands as well.</li><li><a shape="rect" href="graceful-shutdown.html">Graceful Shutdown</a> now logs information about the inflight exchanges that are still present during shutdown and a timeout was hit.</li><li><a shape="rect" href="message-history.html">Message History</a> which dumps&#160;Exchange information not supports the&#160;<span style="color: rgb(0,0,0);"><a shape="rect" href="how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.html">Exchange.LOG_DEBUG_BODY_MAX_CHARS</a> option to limit the max chars outputted in the logs.</span></li><li><code>DefaultClassLoader</code> now fallback and use the application context classloader that may have been set on&#160;<code>CamelContext</code> to better be able to load classes/resources from classpath in different runtime environments.<span style="color: rgb(0,0,0);"><br clear="none"></span></li><li><a shape="rect" href="camel-jmx.htm
 l">Camel JMX</a> now includes current inflight exchanges at processor level, which means we can have a complete breakdown where exchanges are, and as well from the improved&#160;<code>InflightRegistry</code> which has APi and JMX api to browse the current inflight with details of the exchange and processing times etc.</li><li>Support for Jetty 9 using the new&#160;<code>camel-component-jetty9</code> module.</li><li>The&#160;<code>EndpointRegistry</code> now stores endpoints in two caches; a static unbounded cache to keep endpoints for their lifetime, and a dynamic limited cache to keep only the recently used endpoints.&#160;</li><li><a shape="rect" href="endpoint.html">Endpoint</a>'s used by routes are kept in the static cache of the&#160;<code>EndpointRegistry</code> as long as the lifetime of the routes.</li><li>Removing a route now also remove its static&#160;<a shape="rect" href="endpoint.html">Endpoint</a>'s from the&#160;<code>EndpointRegistry</code> (if those endpoints are no
 t shared and used by other routes). Mind that any dynamic endpoint created during routing from dynamic&#160;<a shape="rect" href="eip.html">EIP</a>s such as recipient list, routing slip, dynamic router etc, are not removed from the <code>EndpointRegistry</code>&#160;when the route is removed.</li><li><a shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a> now logs a WARN if a new exception occurred while it was attempting to process the dead letter message. The new exception will by default be handled so the&#160;<a shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a> always complete succesfull. The new option&#160;<span>deadLetterHandleNewException</span><span>&#160;can be set to&#160;<code>false</code> to turn this off.</span></li><li><span><a shape="rect" href="groovy.html">GroovyShell</a> creation process can now be <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-8259">customized</a> using <code>GroovyShellF
 actory</code> SPI interface.</span></li><li><a shape="rect" href="how-do-i-configure-endpoints.html">Configuring endpoint uris in XML DSL</a> now allow to specify the uri attribute using multiple lines; this can make it more readable when having very long uris. Notice only the uri attributes support this.</li></ul><h3 id="Camel2.15.0Release-Fixedissues">Fixed issues</h3><ul><li>Fixed processors was not enlisted in JMX when routes was transacted.</li><li>Fixed the NullPointerException when using CXF endpoint with enrich</li><li>Fixed the&#160;endpointProperty of&#160;restConfiguration doesn't work issue</li><li>Fixed the issue that&#160;CircuitBreakerLoadBalancer fails on async processors</li><li>Fixed&#160;MyBatis consumer <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CAMEL-8011">ignoring maxMessagesPerPoll</a> option</li><li>Fixed potential issue with&#160;pollEnrich not triggering error handler if an exception was thrown in the polling.</li><li>
 Fixed a memory leak if using&#160;<a shape="rect" href="dynamic-router.html">Dynamic Router</a> that loops many times, and uses&#160;any of&#160;<code>convertBodyTo</code> or&#160;<code>setBody</code> or&#160;<code>transform</code> in the loop, causing memory to stack up until the Exchange is done.</li><li>Fixed and improved how&#160;<a shape="rect" href="bean.html">Bean</a>&#160;component and&#160;<a shape="rect" href="simple.html">Simple</a>&#160;language invoking beans detect methods that are overridden, and able to filter and apply this as a single method, to be invoked. Avoids AmbiguousMethodCallException&#160;being thrown.</li><li>Fixed a thread leak if restarting routes using stop/start and the routes is a scheduled poll consumer, such as file/ftp&#160;components.</li><li>Using ?exchangePattern=InOnly or InOut in endpoint uris now take precedence as the pattern in use when sending to the endpoint, using to/recipient list.</li><li><a shape="rect" href="mail.html">Mail</a>&#160
 ;component no longer includes headers starting with&#160;<code>Camel</code> in their keys, as those are consider internal headers and should not be included in the sent emails.<br clear="none"><br clear="none"></li></ul><h3 id="Camel2.15.0Release-New">New <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a></h3><h3 id="Camel2.15.0Release-New.1">New <a shape="rect" href="components.html">Components</a></h3><ul><li><a shape="rect" href="beanstalk.html">camel-beanstalk</a> - for working with Amazon Beanstalk jobs.</li><li>came-cassandraql -&#160;Cassandra CQL3 support</li><li><code>camel-chunk</code> - for templating with Chunk engine.</li><li><a shape="rect" href="docker.html">camel-docker</a> - to communicate with Docker.</li><li>camel-github - for integrating with github</li><li>camel-google-calendar -&#160;provides access to&#160;<a shape="rect" class="external-link" href="http://google.com/calendar" rel="nofollow">Google Calendar</a>&#160
 ;via the&#160;<a shape="rect" class="external-link" href="https://developers.google.com/google-apps/calendar/v3/reference/" rel="nofollow">Google Calendar Web APIs</a>.</li><li>camel-google-mail -&#160;provides access to&#160;<a shape="rect" class="external-link" href="http://gmail.com/" rel="nofollow">Gmail</a>&#160;via the&#160;<a shape="rect" class="external-link" href="https://developers.google.com/gmail/api/v1/reference/" rel="nofollow">Google Mail Web APIs</a>.</li><li><a shape="rect" href="hipchat.html">camel-hipchat</a> - to integrate with the Hipchat service</li><li>camel-pgevent -&#160;Component for sending/receiving notifications in PostgreSQL via the pgjdbc-ng driver</li><li>camel-jira - for integrating with JIRA issue tracker</li><li>camel-scr - for using Camel with <a shape="rect" class="external-link" href="http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html">SCR</a>&#160;(OSGi declarative services) on OSGi containers s
 uch as Apache Karaf</li><li><a shape="rect" href="spring-boot.html">camel-spring-boot</a> - for using Camel with Spring Boot</li><li>camel-test-spring40 - for testing with Spring 4.0.x. camel-test-spring is for Spring 4.1.x onwards.</li></ul><h3 id="Camel2.15.0Release-NewDSL">New DSL</h3><ul><li>Added <strong>removeProperties</strong> to remove the properties from exchange.</li></ul><h3 id="Camel2.15.0Release-NewAnnotations">New Annotations</h3><h3 id="Camel2.15.0Release-NewDataFormats">New <a shape="rect" href="data-format.html">Data Formats</a></h3><ul><li>camel-univocity-parsers</li></ul><h3 id="Camel2.15.0Release-New.2">New <a shape="rect" href="languages.html">Languages</a></h3><h3 id="Camel2.15.0Release-New.3">New <a shape="rect" href="examples.html">Examples</a></h3><h3 id="Camel2.15.0Release-New.4">New <a shape="rect" href="tutorials.html">Tutorials</a></h3><h2 id="Camel2.15.0Release-KnownIssues">Known Issues</h2><h2 id="Camel2.15.0Release-DependencyUpgrades"><span>Dependenc
 y Upgrades</span></h2><ul><li>AWS-Java-SDK 1.8.3 to 1.8.9.1</li><li>Codahale Metrics 3.0 to 3.1</li><li>CXF 3.0.2 to 3.0.3</li><li>Hazelcast 3.3.2 to 3.4</li><li>JAXB 2.2.7 to 2.2.11</li><li>JRuby 1.7.16 to 1.7.18</li><li>Guava 17.0 to 18.0</li><li>Jsch 0.1.50 to 0.1.51</li><li>JsonPath 1.1.0 to 1.2.0</li><li>Spring 4.0.7.RELEASE to 4.1.4.RELEASE</li><li>Spring Security 3.1.7.RELEASE to 3.2.5.RELEASE</li><li>RX Java 0.20 to 1.0.4</li><li>... and many other upgrades</li></ul><h2 id="Camel2.15.0Release-Importantchangestoconsiderwhenupgrading">Important changes to consider when upgrading</h2><ul><li>Spring 4.1.x is now the default out of the box Spring version.</li><li><span style="color: rgb(0,0,0);">Unit testing with Spring 4.0.x requires using camel-test-spring40, as camel-test-spring is for Spring 4.1 or better.</span></li><li><span style="color: rgb(0,0,0);">Remember to add&#160;<code class="java color1">@BootstrapWith</code><code class="java plain">(CamelTestContextBootstrapper.<
 /code><code class="java keyword">class</code><code class="java plain">)</code>&#160;if upgrading from Spring 3.x or 4.0.x to Spring 4.1 onwards, and using the camel-test-spring module.</span></li><li><a shape="rect" href="xslt.html">XSLT</a>&#160;component now require configuring&#160;<code>transformerFactory</code> using&#160;<a shape="rect" href="uris.html">URIs</a> with the #syntax to refer to a bean. Just like any other component would do.</li><li>Slight refactor in&#160;<code>camel-metrics</code> component which may affect users who are using the java endpoint types instead of configuring using uris</li><li><code>camel-csv</code> upgraded to Commons CSV 1.x which has a different API than the old 0.x version. End users may need to adjust their code.</li><li><code>camel-sjms</code> has been refactored a bit to further harden this component.&#160;End users may need to adjust their code.</li><li>The <a shape="rect" href="simple.html">simple</a> function properties:locations:key has
  been renamed to properties-location:locations:key, as it would clash with the new functionality to specify a default value after the key name, eg properties:key:default</li><li>Removed the backlog tracer commands from the Karaf Camel commands as they are not suitable for a CLI environment</li><li>The need for runtime specific servlets in <a shape="rect" href="swagger.html">Swagger</a>&#160;has been removed, and instead just use the default servlet which is provided out of the box.&#160;</li><li><code>org.apache.camel.spi.InflightRepository</code> now includes additional methods for browsing in-flight exchanges.</li><li>Using ?exchangePattern=InOnly or InOut in endpoint uris now take precedence as the pattern in use when sending to the endpoint, using to/recipient list.</li><li><code>DefaultClassLoader</code> now fallback and use the application context classloader that may have been set on&#160;<code>CamelContext</code> to better be able to load classes/resources from classpath in 
 different runtime environments.</li><li><a shape="rect" href="mail.html">Mail</a>&#160;component no longer includes headers starting with&#160;<code>Camel</code> in their keys, as those are consider internal headers and should not be included in the sent emails.</li><li>Removing a route now also remove its static&#160;<a shape="rect" href="endpoint.html">Endpoint</a>'s from the&#160;<code>EndpointRegistry</code> (if those endpoints are not shared and used by other routes). Mind that any dynamic endpoint created during routing from dynamic&#160;<a shape="rect" href="eip.html">EIP</a>s such as recipient list, routing slip, dynamic router etc, are not removed from the <code>EndpointRegistry</code>&#160;when the route is removed.</li><li>All boolean isFoo methods on the model classes has been removed to ensure the model has consistent java bean getter/setter style with exactly one getter and one setter of the same type.<br clear="none"><br clear="none"></li></ul><h2 id="Camel2.15.0Relea
 se-GettingtheDistributions">Getting the Distributions</h2><h3 id="Camel2.15.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.15.0/apache-camel-x.y.x.zip">apache-camel-2.15.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.15.0/apache-camel-x.y.x.zip.asc">apache-camel-2.15.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.15.0/apache-camel-x.y.x.tar.gz">apache-camel-2.15.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.15.0/apache-camel-x.y.x.tar.gz.asc">apache-camel-2.15.0.tar.gz.asc</a></p></td></tr></tbody></table></div>    <div class="aui-message 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/how-do-i-configure-endpoints.html
==============================================================================
--- websites/production/camel/content/how-do-i-configure-endpoints.html (original)
+++ websites/production/camel/content/how-do-i-configure-endpoints.html Mon Feb  2 21:18:22 2015
@@ -86,32 +86,11 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="HowdoIconfigureendpoints-HowdoIconfigureendpoints?">How do I configure endpoints?</h2>
-
-<p>There are a few different approaches to configuring components and endpoints. </p>
-
-<h3 id="HowdoIconfigureendpoints-UsingJavaCode">Using Java Code</h3>
-
-<p>You can explicitly configure a <a shape="rect" href="component.html">Component</a> using Java code as shown in this <a shape="rect" href="walk-through-an-example.html">example</a> </p>
-
-<p>Or you can explicitly get hold of an <a shape="rect" href="endpoint.html">Endpoint</a> and configure it using Java code as shown in the <a shape="rect" href="mock.html">Mock endpoint examples</a>.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-SomeEndpoint endpoint = camelContext.getEndpoint(&quot;someURI&quot;, SomeEndpoint.class);
+<div class="wiki-content maincontent"><h2 id="HowdoIconfigureendpoints-HowdoIconfigureendpoints?">How do I configure endpoints?</h2><p>There are a few different approaches to configuring components and endpoints.</p><h3 id="HowdoIconfigureendpoints-UsingJavaCode">Using Java Code</h3><p>You can explicitly configure a <a shape="rect" href="component.html">Component</a> using Java code as shown in this <a shape="rect" href="walk-through-an-example.html">example</a></p><p>Or you can explicitly get hold of an <a shape="rect" href="endpoint.html">Endpoint</a> and configure it using Java code as shown in the <a shape="rect" href="mock.html">Mock endpoint examples</a>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[SomeEndpoint endpoint = camelContext.getEndpoint(&quot;someURI&quot;, SomeEndpoint.class);
 endpoint.setSomething(&quot;aValue&quot;);
 ]]></script>
-</div></div>
-
-<h3 id="HowdoIconfigureendpoints-UsingGuice">Using Guice</h3>
-
-<p>You can also use <a shape="rect" href="guice.html">Guice</a> as the dependency injection framework. For example see the <a shape="rect" href="guice-jms-example.html">Guice JMS Example</a></p>
-
-<h3 id="HowdoIconfigureendpoints-UsingSpringXML">Using Spring XML</h3>
-
-<p>You can configure your <a shape="rect" href="component.html">Component</a> or <a shape="rect" href="endpoint.html">Endpoint</a> instances in your <a shape="rect" href="spring.html">Spring</a> XML as follows. </p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="HowdoIconfigureendpoints-UsingGuice">Using Guice</h3><p>You can also use <a shape="rect" href="guice.html">Guice</a> as the dependency injection framework. For example see the <a shape="rect" href="guice-jms-example.html">Guice JMS Example</a></p><h3 id="HowdoIconfigureendpoints-UsingSpringXML">Using Spring XML</h3><p>You can configure your <a shape="rect" href="component.html">Component</a> or <a shape="rect" href="endpoint.html">Endpoint</a> instances in your <a shape="rect" href="spring.html">Spring</a> XML 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;camelContext id=&quot;camel&quot; xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
     &lt;jmxAgent id=&quot;agent&quot; disabled=&quot;true&quot;/&gt;
@@ -125,94 +104,49 @@ endpoint.setSomething(&quot;aValue&quot;
   &lt;/property&gt;
 &lt;/bean&gt;
 ]]></script>
-</div></div>
-
-<p>Which allows you to configure a component using some name (activemq in the above example), then you can refer to the component using <strong>activemq:[queue:|topic:]destinationName</strong>. This works by the SpringCamelContext lazily fetching components from the spring context for the scheme name you use for <a shape="rect" href="endpoint.html">Endpoint</a> <a shape="rect" href="uris.html">URIs</a></p>
-
-<h3 id="HowdoIconfigureendpoints-UsingEndpointURIs">Using Endpoint URIs</h3>
-
-<p>Another approach is to use the URI syntax. The URI syntax supports the query notation. So for example with the <a shape="rect" href="mail.html">Mail</a> component you can configure the password property via the 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[
-pop3://host:port?password=foo
+</div></div><p>Which allows you to configure a component using some name (activemq in the above example), then you can refer to the component using <strong>activemq:[queue:|topic:]destinationName</strong>. This works by the SpringCamelContext lazily fetching components from the spring context for the scheme name you use for <a shape="rect" href="endpoint.html">Endpoint</a> <a shape="rect" href="uris.html">URIs</a></p><h3 id="HowdoIconfigureendpoints-UsingEndpointURIs">Using Endpoint URIs</h3><p>Another approach is to use the URI syntax. The URI syntax supports the query notation. So for example with the <a shape="rect" href="mail.html">Mail</a> component you can configure the password property via the 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[pop3://host:port?password=foo
 ]]></script>
-</div></div>
-
-<h4 id="HowdoIconfigureendpoints-ReferringbeansfromEndpointURIs">Referring beans from Endpoint URIs </h4>
-<p><strong>Available as of Camel 2.0</strong></p>
-
-<p>When configuring endpoints using URI syntax you can now refer to beans in the <a shape="rect" href="registry.html">Registry</a> using the # notation.<br clear="none">
-If the parameter value starts with a <code>#</code> sign then Camel will lookup in the <a shape="rect" href="registry.html">Registry</a> for a bean of the given type. For instance:</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[
-file://inbox?sorter=#mySpecialFileSorter
+</div></div><h4 id="HowdoIconfigureendpoints-ReferringbeansfromEndpointURIs">Referring beans from Endpoint URIs</h4><p><strong>Available as of Camel 2.0</strong></p><p>When configuring endpoints using URI syntax you can now refer to beans in the <a shape="rect" href="registry.html">Registry</a> using the # notation.<br clear="none"> If the parameter value starts with a <code>#</code> sign then Camel will lookup in the <a shape="rect" href="registry.html">Registry</a> for a bean of the given type. For instance:</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[file://inbox?sorter=#mySpecialFileSorter
 ]]></script>
-</div></div>
-<p>Will lookup a bean with the id <strong>mySpecialFileSorter</strong> in the <a shape="rect" href="registry.html">Registry</a>.</p>
-
-<h4 id="HowdoIconfigureendpoints-Configuringparametervaluesusingrawvalues,egsuchaspasswords">Configuring parameter values using raw values, eg such as passwords</h4>
-<p><strong>Available as of Camel 2.11</strong></p>
-
-<p>When configuring endpoint options using URI syntax, then the values is by default URI encoded. This can be a problem if you want to configure passwords and just use the value <em>as is</em> without any encoding. For example you may have a plus sign in the password, which would be decimal encoded by default.</p>
-
-<p>So from Camel 2.11 onwards we made this easier as you can denote a parameter value to be <strong>raw</strong> using the following syntax <code>RAW(value)</code>. eg the value starts with <code>RAW(</code> and then ends with the parenthesis <code>)</code>. Here is a little 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[
-.to(&quot;ftp:joe@myftpserver.com?password=RAW(se+re?t&amp;23)&amp;binary=true&quot;
+</div></div><p>Will lookup a bean with the id <strong>mySpecialFileSorter</strong> in the <a shape="rect" href="registry.html">Registry</a>.</p><h4 id="HowdoIconfigureendpoints-Configuringparametervaluesusingrawvalues,egsuchaspasswords">Configuring parameter values using raw values, eg such as passwords</h4><p><strong>Available as of Camel 2.11</strong></p><p>When configuring endpoint options using URI syntax, then the values is by default URI encoded. This can be a problem if you want to configure passwords and just use the value <em>as is</em> without any encoding. For example you may have a plus sign in the password, which would be decimal encoded by default.</p><p>So from Camel 2.11 onwards we made this easier as you can denote a parameter value to be <strong>raw</strong> using the following syntax <code>RAW(value)</code>. eg the value starts with <code>RAW(</code> and then ends with the parenthesis <code>)</code>. Here is a little 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[.to(&quot;ftp:joe@myftpserver.com?password=RAW(se+re?t&amp;23)&amp;binary=true&quot;
 ]]></script>
-</div></div>
-
-<p>In the above example, we have declare the password value as raw, and the actual password would be as typed, eg <code>se+re?t&amp;23</code>.</p>
-
-<h4 id="HowdoIconfigureendpoints-Usingpropertyplaceholders">Using property placeholders</h4>
-
-<p>Camel have extensive support for using property placeholders, which you can read more <a shape="rect" href="using-propertyplaceholder.html">about here</a>. For example in the ftp example above we can externalize the password to a .properties file.</p>
-
-<p>For example configuring the property placeholder when using a <a shape="rect" href="dsl.html">XML DSL</a>, where we declare the location of the .properties file. Though we can also define this in Java code. See the <a shape="rect" href="using-propertyplaceholder.html">documentation</a> for more details.</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>In the above example, we have declare the password value as raw, and the actual password would be as typed, eg <code>se+re?t&amp;23</code>.</p><h4 id="HowdoIconfigureendpoints-Usingpropertyplaceholders">Using property placeholders</h4><p>Camel have extensive support for using property placeholders, which you can read more <a shape="rect" href="using-propertyplaceholder.html">about here</a>. For example in the ftp example above we can externalize the password to a .properties file.</p><p>For example configuring the property placeholder when using a <a shape="rect" href="dsl.html">XML DSL</a>, where we declare the location of the .properties file. Though we can also define this in Java code. See the <a shape="rect" href="using-propertyplaceholder.html">documentation</a> for more details.</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;myftp.properties&quot;/&gt;
    ...
 &lt;/camelContext&gt;
 ]]></script>
-</div></div>
-
-<p>And the Camel route now refers to the placeholder using the {{ key }} notation:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-.to(&quot;ftp:joe@myftpserver.com?password={{myFtpPassword}}&amp;binary=true&quot;
-]]></script>
-</div></div>
-
-<p>And have a myftp.properties file with password. Notice we still define the RAW(value) style to ensure the password is used <em>as is</em> </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[
-myFtpPassword=RAW(se+re?t&amp;23)
+</div></div><p>And the Camel route now refers to the placeholder using the {{ key }} notation:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[.to(&quot;ftp:joe@myftpserver.com?password={{myFtpPassword}}&amp;binary=true&quot;
 ]]></script>
-</div></div>
-
-<p>We could still have used the RAW(value) in the Camel route instead:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-.to(&quot;ftp:joe@myftpserver.com?password=RAW({{myFtpPassword}})&amp;binary=true&quot;
+</div></div><p>And have a myftp.properties file with password. Notice we still define the RAW(value) style to ensure the password is used <em>as is</em></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[myFtpPassword=RAW(se+re?t&amp;23)
 ]]></script>
-</div></div>
-
-<p>And then we would need to remove the RAW from the properties file:</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[
-myFtpPassword=se+re?t&amp;23
+</div></div><p>We could still have used the RAW(value) in the Camel route instead:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[.to(&quot;ftp:joe@myftpserver.com?password=RAW({{myFtpPassword}})&amp;binary=true&quot;
 ]]></script>
-</div></div>
-
-<p>To understand more about property placeholders, read the <a shape="rect" href="using-propertyplaceholder.html">documentation</a>.</p>
-
-<h2 id="HowdoIconfigureendpoints-SeeAlso">See Also</h2>
-
-<ul><li><a shape="rect" href="how-do-i-add-a-component.html">How do I add a component</a></li><li><a shape="rect" href="spring.html">Spring</a></li><li><a shape="rect" href="uris.html">URIs</a></li><li><a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a></li></ul></div>
+</div></div><p>And then we would need to remove the RAW from the properties file:</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[myFtpPassword=se+re?t&amp;23
+]]></script>
+</div></div><p>To understand more about property placeholders, read the <a shape="rect" href="using-propertyplaceholder.html">documentation</a>.</p><h3 id="HowdoIconfigureendpoints-Configuringlongurisusingnewlines">Configuring long uris using new lines</h3><p><strong>Available as of Camel 2.15</strong></p><p>Sometimes configuring endpoint uris may have many options, and therefore the uri can become long. In Java DSL you can break the uris into new lines as its just Java code, eg just concat the String. When using XML DSL then the uri is an attribute, eg &lt;from uri="bla bla"/&gt;. From Camel 2.15 onwards you can break the uri attribute using new line, such 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;route&gt;
+  &lt;from uri=&quot;ftp://foo@myserver?password=secret&amp;amp;
+           recursive=true&amp;amp;
+           ftpClient.dataTimeout=30000&amp;amp;
+           ftpClientConfig.serverLanguageCode=fr&quot;/&gt;
+  &lt;to uri=&quot;bean:doSomething&quot;/&gt;
+&lt;/route&gt;]]></script>
+</div></div><p>Notice that it still requires to use escape &amp; as &amp;ampl; in XML. Also you can have multiple options in one line, eg this is the same:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;route&gt;
+  &lt;from uri=&quot;ftp://foo@myserver?password=secret&amp;amp;
+           recursive=true&amp;amp;ftpClient.dataTimeout=30000&amp;amp;
+           ftpClientConfig.serverLanguageCode=fr&quot;/&gt;
+  &lt;to uri=&quot;bean:doSomething&quot;/&gt;
+&lt;/route&gt;]]></script>
+</div></div><h2 id="HowdoIconfigureendpoints-SeeAlso"><span style="line-height: 1.5;">See Also</span></h2><ul><li><a shape="rect" href="how-do-i-add-a-component.html">How do I add a component</a></li><li><a shape="rect" href="spring.html">Spring</a></li><li><a shape="rect" href="uris.html">URIs</a></li><li><a shape="rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a></li></ul></div>
         </td>
         <td valign="top">
           <div class="navigation">



Mime
View raw message