Author: buildbot
Date: Tue Sep 10 15:18:55 2013
New Revision: 877922
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-2130-release.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-2130-release.html
==============================================================================
--- websites/production/camel/content/camel-2130-release.html (original)
+++ websites/production/camel/content/camel-2130-release.html Tue Sep 10
15:18:55 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>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="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 concurrent processing in the
route.</li></ul>
+<ul><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="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 concurrent 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></ul>
<h3><a shape="rect" name="Camel2.13.0Release-FixedIssues"></a>Fixed Issues</h3>
