Author: buildbot
Date: Thu Nov 28 09:19:51 2013
New Revision: 888374
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/advanced-configuration-of-camelcontext-using-spring.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-2130-release.html
Modified:
websites/production/camel/content/advanced-configuration-of-camelcontext-using-spring.html
==============================================================================
---
websites/production/camel/content/advanced-configuration-of-camelcontext-using-spring.html
(original)
+++
websites/production/camel/content/advanced-configuration-of-camelcontext-using-spring.html
Thu Nov 28 09:19:51 2013
@@ -100,7 +100,7 @@ When Camel finds and uses any of these i
<p>The following list all requires at most 1 beans defined. If there are more
than 1 bean of this type, then Camel will <b>not</b> use it. </p>
<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Number of beans </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> PackageScanClassResolver </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> To use a 3rd party package scan resolver. More details at
<a shape="rect" href="pluggable-class-resolvers.html" title="Pluggable Class
Resolvers">Pluggable Class Resolvers</a>. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> ClassResolver </td><td colspan="1"
rowspan="1" class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> To use a 3rd party class resolver. More details at <a
shape="rect" href="pluggable-class-resolvers.html" title="Pluggable Class
Resolvers">Pluggable Class Resolvers</a>. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> FactoryFinderResolver </td><td
colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td colspan="1"
rowspan="1" class="confluenceTd"> To use a 3rd party factory finder.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Registry
</td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td
colspan="1" rowspan="1" class="confluenceTd"> To use a 3rd party bean registry.
By default Camel will use Spring ApplicationContext as registry.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Debugger
</td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td
colspan="1" rowspan="1" class="confluenceTd"> To use a <a shape="rect"
href="debugger.html" title="Debugger">Debugger</a> usually for tooling.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Tracer </td><td
colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td colspan="1"
rowspan="1" class="confluenceTd"> To use a 3rd party <a
shape="rect" href="tracer.html" title="Tracer">Tracer</a>. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> TraceFormatter </td><td
colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td colspan="1"
rowspan="1" class="confluenceTd"> To use a bean that has the tracing options
configured. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
HandleFault </td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1
</td><td colspan="1" rowspan="1" class="confluenceTd"> To use a 3rd part fault
handler to handle FAULT messages. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> Delayer </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> To use a 3rd part <a shape="rect" href="delayer.html"
title="Delayer">Delayer</a>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> ManagementStrategy </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowsp
an="1" class="confluenceTd"> <b>Camel 2.1:</b> To use a 3rd part strategy for
<a shape="rect" href="camel-jmx.html" title="Camel JMX">management</a>, for
example JMX management. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> ManagementNamingStrategy </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.6:</b> To use a 3rd part strategy for naming
MBeans for <a shape="rect" href="camel-jmx.html" title="Camel
JMX">management</a>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> NodeIdFactory </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.10:</b> To use a 3rd part node id factory.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> EventFactory
</td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> To use a 3rd
part e
vent factory. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
EventNotifier </td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1
</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> To use
a 3rd part event notifier. In Camel 2.2 onwards you can have multiple
notifiers, see next table.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> InflightRepository </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.1:</b> To use a 3rd part inflight repository.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
ShutdownStrategy </td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1
</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.2:</b> To use
a 3rd part shutdown strategy. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> ExecutorServiceStrategy </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspa
n="1" rowspan="1" class="confluenceTd"> <b>Camel 2.3 - 2.8.x:</b> To use a 3rd
part executor service strategy. More details at <a shape="rect"
href="threading-model.html" title="Threading Model">Threading Model</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
ExecutorServiceManager </td><td colspan="1" rowspan="1" class="confluenceTd">
0..1 </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b>
To use a 3rd part executor service manager. More details at <a shape="rect"
href="threading-model.html" title="Threading Model">Threading Model</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
ThreadPoolFactory </td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1
</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> To use
a 3rd part thread pool factory. More details at <a shape="rect"
href="threading-model.html" title="Threading Model">Threading Model</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="conf
luenceTd"> ProcessorFactory </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.4:</b> To use a 3rd part processor factory.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> UuidGenerator
</td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5:</b> To use a 3rd
part <a shape="rect" href="uuidgenerator.html"
title="UuidGenerator">UuidGenerator</a>. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> StreamCachingStrategy </td><td colspan="1"
rowspan="1" class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.12:</b> To use a 3rd part <a shape="rect"
href="stream-caching.html" title="Stream caching">Stream caching</a> strategy.
</td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Number of beans </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> PackageScanClassResolver </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> To use a 3rd party package scan resolver. More details at
<a shape="rect" href="pluggable-class-resolvers.html" title="Pluggable Class
Resolvers">Pluggable Class Resolvers</a>. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> ClassResolver </td><td colspan="1"
rowspan="1" class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> To use a 3rd party class resolver. More details at <a
shape="rect" href="pluggable-class-resolvers.html" title="Pluggable Class
Resolvers">Pluggable Class Resolvers</a>. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> FactoryFinderResolver </td><td
colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td colspan="1"
rowspan="1" class="confluenceTd"> To use a 3rd party factory finder.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Registry
</td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td
colspan="1" rowspan="1" class="confluenceTd"> To use a 3rd party bean registry.
By default Camel will use Spring ApplicationContext as registry.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Debugger
</td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td
colspan="1" rowspan="1" class="confluenceTd"> To use a <a shape="rect"
href="debugger.html" title="Debugger">Debugger</a> usually for tooling.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> Tracer </td><td
colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td colspan="1"
rowspan="1" class="confluenceTd"> To use a 3rd party <a
shape="rect" href="tracer.html" title="Tracer">Tracer</a>. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> TraceFormatter </td><td
colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td colspan="1"
rowspan="1" class="confluenceTd"> To use a bean that has the tracing options
configured. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
HandleFault </td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1
</td><td colspan="1" rowspan="1" class="confluenceTd"> To use a 3rd part fault
handler to handle FAULT messages. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> Delayer </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> To use a 3rd part <a shape="rect" href="delayer.html"
title="Delayer">Delayer</a>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> ManagementStrategy </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowsp
an="1" class="confluenceTd"> <b>Camel 2.1:</b> To use a 3rd part strategy for
<a shape="rect" href="camel-jmx.html" title="Camel JMX">management</a>, for
example JMX management. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> ManagementNamingStrategy </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.6:</b> To use a 3rd part strategy for naming
MBeans for <a shape="rect" href="camel-jmx.html" title="Camel
JMX">management</a>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> NodeIdFactory </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.10:</b> To use a 3rd part node id factory.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> EventFactory
</td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> To use a 3rd
part e
vent factory. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
EventNotifier </td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1
</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> To use
a 3rd part event notifier. In Camel 2.2 onwards you can have multiple
notifiers, see next table.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> InflightRepository </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.1:</b> To use a 3rd part inflight repository.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
ShutdownStrategy </td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1
</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.2:</b> To use
a 3rd part shutdown strategy. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> ExecutorServiceStrategy </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspa
n="1" rowspan="1" class="confluenceTd"> <b>Camel 2.3 - 2.8.x:</b> To use a 3rd
part executor service strategy. More details at <a shape="rect"
href="threading-model.html" title="Threading Model">Threading Model</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
ExecutorServiceManager </td><td colspan="1" rowspan="1" class="confluenceTd">
0..1 </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b>
To use a 3rd part executor service manager. More details at <a shape="rect"
href="threading-model.html" title="Threading Model">Threading Model</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
ThreadPoolFactory </td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1
</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> To use
a 3rd part thread pool factory. More details at <a shape="rect"
href="threading-model.html" title="Threading Model">Threading Model</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="conf
luenceTd"> ProcessorFactory </td><td colspan="1" rowspan="1"
class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.4:</b> To use a 3rd part processor factory.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> UuidGenerator
</td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1 </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5:</b> To use a 3rd
part <a shape="rect" href="uuidgenerator.html"
title="UuidGenerator">UuidGenerator</a>. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> StreamCachingStrategy </td><td colspan="1"
rowspan="1" class="confluenceTd"> 0..1 </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.12:</b> To use a 3rd part <a shape="rect"
href="stream-caching.html" title="Stream caching">Stream caching</a> strategy.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
UnitOfWorkFactory </td><td colspan="1" rowspan="1" class="confluenceTd"> 0..1
</td><td col
span="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12.3/2.13:</b> To use
3rd part <tt>UnitOfWork</tt> implementations created by the factory.
</td></tr></tbody></table>
</div>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-2130-release.html
==============================================================================
--- websites/production/camel/content/camel-2130-release.html (original)
+++ websites/production/camel/content/camel-2130-release.html Thu Nov 28
09:19:51 2013
@@ -94,7 +94,7 @@
<p>Welcome to the 2.13.0 release which approx XXX issues resolved (new
features, improvements and bug fixes such as...)</p>
-<ul><li>The MBean names registered by <a shape="rect" href="camel-jmx.html"
title="Camel JMX">Camel JMX</a> no longer include the hostname in the
<tt>context</tt> part, eg before <tt>context=myHost/myCamelId</tt> and now
after <tt>context=myCamelId</tt>. Having the hostname in the MBean name does
not bring much value, and in fact makes things more complicated as the mbean
name changes depending on the host running Camel.</li><li><a shape="rect"
href="camel-jmx.html" title="Camel JMX">MBean naming</a> in OSGi cleaned up to
use simpler naming with symbolicName. Before we could have MBean names with
duplicate bundle ids such as <tt>context=114-114-camel-6</tt>, which now is
using the symbolic name instead, <tt>context=MyApplication</tt>.</li><li>When
using multiple OSGi Blueprint <cm:property-placeholder>'s then Camel now
favors using non-default placeholders, or the last property-placeholder defined
in the Blueprint XML file. This allows for example to define default properties
in one placeholder, and override these values in other
placeholders.</li><li><a shape="rect" href="ftp2.html" title="FTP2">FTP</a>
consumer allow to download a single named file without using the FTP LIST
command. This allows to download a known file from a FTP server even when the
user account does not have permission to do FTP LIST command.</li><li><a
shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer allow to ignore
file not found or insufficient file permission errors.</li><li><a shape="rect"
href="data-format.html" title="Data Format">Data Format</a> using marshal now
leverages <a shape="rect" href="stream-caching.html" title="Stream
caching">Stream caching</a> out of the box if enabled, which allows to marshal
big streams and spool to disk, instead of being pure in-memory
based.</li><li>Improved using <a shape="rect" href="bean.html"
title="Bean">Bean</a> when the bean is looked up in the <a shape="rect"
href="registry.html" title="Registry">Registry</a>, when using c
oncurrent processing in the route.</li><li>Added <tt>cache</tt> option to
<tt>beanRef</tt> and <tt><bean></tt> in the DSL. This avoids looking up
the <a shape="rect" href="bean.html" title="Bean">Bean</a> from the <a
shape="rect" href="registry.html" title="Registry">Registry</a> on each usage;
this can safely be done for singleton beans.</li><li>Configuring <a
shape="rect" href="data-format.html" title="Data Format">Data Format</a>s in
XML attributes now supports reference lookup using the # syntax, eg
<tt><jaxb xmlStreamWriterWrapper="#myWriterWrapper" ..></tt></li><li><a
shape="rect" href="jdbc.html" title="JDBC">JDBC</a> component now also support
<tt>outputType</tt> to specify the expected output as either a List or single
Object. As well allow to map to a bean using a <tt>BeanRowMapper</tt> to
control the mapping of ROW names to bean properties.</li><li>Both <a
shape="rect" href="quartz.html" title="Quartz">Quartz</a> as well as <a
shape="rect" href="quartz2.html"
title="Quartz2">Quartz2</a> based <a shape="rect"
href="scheduledroutepolicy.html"
title="ScheduledRoutePolicy">ScheduledRoutePolicy</a> has been improved to
better support cluster setups (e.g. to not schedule jobs being already
scheduled through another node inside a given cluster).</li><li>Reduced the
work the <a shape="rect" href="aggregator2.html"
title="Aggregator2">Aggregate</a> EIP does while holding a lock during
aggregation, which can lead to improved performance in some
use-cases.</li><li><tt>JndiRegistry</tt> now implements all the find
methods.</li><li><a shape="rect" href="vm.html" title="VM">VM</a> component now
supports <tt>multipleConsumers=true</tt> across deployment units.</li><li>Added
<tt>@PreConsumed</tt> to <a shape="rect" href="jpa.html" title="JPA">JPA</a>
consumer.</li><li>Added CamelFileName header support to the <a shape="rect"
href="hdfs.html" title="HDFS">HDFS</a> producer</li><li>Like as
<tt>JpaConsumer</tt> now also <tt>JpaProducer</tt> of the <a shape
="rect" href="jpa.html" title="JPA">JPA</a> component supports the
<tt>CamelEntityManager</tt> header.</li><li><a shape="rect" href="restlet.html"
title="Restlet">Restlet</a> consumer now supports returning custom headers as
HTTP headers from the Camel <a shape="rect" href="message.html"
title="Message">Message</a>.</li><li><a shape="rect"
href="spring-java-config.html" title="Spring Java Config">Spring Java
Config</a> <tt>CamelConfiguration</tt> now automagically detects all
<tt>RouteBuilder</tt> instances registered in the Spring context if
<tt>CamelConfiguration#routes</tt> method is not overridden.</li><li>Added
support for transferring custom headers with <a shape="rect"
href="rabbitmq.html" title="RabbitMQ">RabbitMQ</a> component.</li><li><a
shape="rect" href="crypto.html" title="Crypto">PGPDataFormat</a> enables stream
cache during unmarshaling.</li><li><tt>FileIdempotentRepository</tt> now
creates necessary parent directories together with the new repository
file.</li><li><a
shape="rect" href="properties.html" title="Properties">Properties</a>
component and <a shape="rect" href="using-propertyplaceholder.html"
title="Using PropertyPlaceholder">property placeholder</a> will now ignore non
existing JVM and environment options as well if <tt>ignoreMissingLocation</tt>
is set to <tt>true</tt>.</li><li>Improved <a shape="rect" href="stream.html"
title="Stream">Stream</a> consumer to enrich the <a shape="rect"
href="message.html" title="Message">Message</a> with headers about current
index / completion flag.</li><li>Added <a shape="rect"
href="bean-injection.html" title="Bean Injection"><tt>@BeanInject</tt></a> to
inject beans (obtained from the <a shape="rect" href="registry.html"
title="Registry">Registry</a>) in your beans such as <tt>RouteBuilder</tt>
classes.</li><li>Polished the <a shape="rect" href="karaf.html"
title="Karaf">Karaf</a> commands to output tables sorted and auto calculated
width, so the data is formatted nicely.</li></ul>
+<ul><li>The MBean names registered by <a shape="rect" href="camel-jmx.html"
title="Camel JMX">Camel JMX</a> no longer include the hostname in the
<tt>context</tt> part, eg before <tt>context=myHost/myCamelId</tt> and now
after <tt>context=myCamelId</tt>. Having the hostname in the MBean name does
not bring much value, and in fact makes things more complicated as the mbean
name changes depending on the host running Camel.</li><li><a shape="rect"
href="camel-jmx.html" title="Camel JMX">MBean naming</a> in OSGi cleaned up to
use simpler naming with symbolicName. Before we could have MBean names with
duplicate bundle ids such as <tt>context=114-114-camel-6</tt>, which now is
using the symbolic name instead, <tt>context=MyApplication</tt>.</li><li>When
using multiple OSGi Blueprint <cm:property-placeholder>'s then Camel now
favors using non-default placeholders, or the last property-placeholder defined
in the Blueprint XML file. This allows for example to define default properties
in one placeholder, and override these values in other
placeholders.</li><li><a shape="rect" href="ftp2.html" title="FTP2">FTP</a>
consumer allow to download a single named file without using the FTP LIST
command. This allows to download a known file from a FTP server even when the
user account does not have permission to do FTP LIST command.</li><li><a
shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer allow to ignore
file not found or insufficient file permission errors.</li><li><a shape="rect"
href="data-format.html" title="Data Format">Data Format</a> using marshal now
leverages <a shape="rect" href="stream-caching.html" title="Stream
caching">Stream caching</a> out of the box if enabled, which allows to marshal
big streams and spool to disk, instead of being pure in-memory
based.</li><li>Improved using <a shape="rect" href="bean.html"
title="Bean">Bean</a> when the bean is looked up in the <a shape="rect"
href="registry.html" title="Registry">Registry</a>, when using c
oncurrent processing in the route.</li><li>Added <tt>cache</tt> option to
<tt>beanRef</tt> and <tt><bean></tt> in the DSL. This avoids looking up
the <a shape="rect" href="bean.html" title="Bean">Bean</a> from the <a
shape="rect" href="registry.html" title="Registry">Registry</a> on each usage;
this can safely be done for singleton beans.</li><li>Configuring <a
shape="rect" href="data-format.html" title="Data Format">Data Format</a>s in
XML attributes now supports reference lookup using the # syntax, eg
<tt><jaxb xmlStreamWriterWrapper="#myWriterWrapper" ..></tt></li><li><a
shape="rect" href="jdbc.html" title="JDBC">JDBC</a> component now also support
<tt>outputType</tt> to specify the expected output as either a List or single
Object. As well allow to map to a bean using a <tt>BeanRowMapper</tt> to
control the mapping of ROW names to bean properties.</li><li>Both <a
shape="rect" href="quartz.html" title="Quartz">Quartz</a> as well as <a
shape="rect" href="quartz2.html"
title="Quartz2">Quartz2</a> based <a shape="rect"
href="scheduledroutepolicy.html"
title="ScheduledRoutePolicy">ScheduledRoutePolicy</a> has been improved to
better support cluster setups (e.g. to not schedule jobs being already
scheduled through another node inside a given cluster).</li><li>Reduced the
work the <a shape="rect" href="aggregator2.html"
title="Aggregator2">Aggregate</a> EIP does while holding a lock during
aggregation, which can lead to improved performance in some
use-cases.</li><li><tt>JndiRegistry</tt> now implements all the find
methods.</li><li><a shape="rect" href="vm.html" title="VM">VM</a> component now
supports <tt>multipleConsumers=true</tt> across deployment units.</li><li>Added
<tt>@PreConsumed</tt> to <a shape="rect" href="jpa.html" title="JPA">JPA</a>
consumer.</li><li>Added CamelFileName header support to the <a shape="rect"
href="hdfs.html" title="HDFS">HDFS</a> producer</li><li>Like as
<tt>JpaConsumer</tt> now also <tt>JpaProducer</tt> of the <a shape
="rect" href="jpa.html" title="JPA">JPA</a> component supports the
<tt>CamelEntityManager</tt> header.</li><li><a shape="rect" href="restlet.html"
title="Restlet">Restlet</a> consumer now supports returning custom headers as
HTTP headers from the Camel <a shape="rect" href="message.html"
title="Message">Message</a>.</li><li><a shape="rect"
href="spring-java-config.html" title="Spring Java Config">Spring Java
Config</a> <tt>CamelConfiguration</tt> now automagically detects all
<tt>RouteBuilder</tt> instances registered in the Spring context if
<tt>CamelConfiguration#routes</tt> method is not overridden.</li><li>Added
support for transferring custom headers with <a shape="rect"
href="rabbitmq.html" title="RabbitMQ">RabbitMQ</a> component.</li><li><a
shape="rect" href="crypto.html" title="Crypto">PGPDataFormat</a> enables stream
cache during unmarshaling.</li><li><tt>FileIdempotentRepository</tt> now
creates necessary parent directories together with the new repository
file.</li><li><a
shape="rect" href="properties.html" title="Properties">Properties</a>
component and <a shape="rect" href="using-propertyplaceholder.html"
title="Using PropertyPlaceholder">property placeholder</a> will now ignore non
existing JVM and environment options as well if <tt>ignoreMissingLocation</tt>
is set to <tt>true</tt>.</li><li>Improved <a shape="rect" href="stream.html"
title="Stream">Stream</a> consumer to enrich the <a shape="rect"
href="message.html" title="Message">Message</a> with headers about current
index / completion flag.</li><li>Added <a shape="rect"
href="bean-injection.html" title="Bean Injection"><tt>@BeanInject</tt></a> to
inject beans (obtained from the <a shape="rect" href="registry.html"
title="Registry">Registry</a>) in your beans such as <tt>RouteBuilder</tt>
classes.</li><li>Polished the <a shape="rect" href="karaf.html"
title="Karaf">Karaf</a> commands to output tables sorted and auto calculated
width, so the data is formatted nicely.</li><li>Introduced <tt>Un
itOfWorkFactory</tt> to allow end users to use custom <tt>UnitOfWork</tt>
implementations created by the factory.</li></ul>
