camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r845228 - in /websites/production/camel/content: cache/main.pageCache camel-2110-release.html
Date Sun, 06 Jan 2013 14:18:06 GMT
Author: buildbot
Date: Sun Jan  6 14:18:06 2013
New Revision: 845228

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-2110-release.html

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

Modified: websites/production/camel/content/camel-2110-release.html
==============================================================================
--- websites/production/camel/content/camel-2110-release.html (original)
+++ websites/production/camel/content/camel-2110-release.html Sun Jan  6 14:18:06 2013
@@ -149,7 +149,7 @@
 
 <h2><a shape="rect" name="Camel2.11.0Release-Importantchangestoconsiderwhenupgrading"></a>Important
changes to consider when upgrading</h2>
 
-<ul><li>Spring 3.0.x support is @deprecated and some of the camel-spring components
require Spring 3.1 onwards.</li><li>Apache Camel Karaf features now uses Spring
version range "[3.1,4)" as Spring 3.1 is now required as minimum Spring version.</li><li><tt>camel-mina2</tt>
now uses <tt>OrderedThreadPoolExecutor</tt> by default. There is a new option
<tt>orderedThreadPoolExecutor</tt> you can configure it to <tt>false</tt>
to revert back to unordered if needed. If using SSL etc. then ordered is required to be used.</li><li><tt>camel-netty</tt>
now uses <tt>OrderedMemoryAwareThreadPoolExecutor</tt> by default. There is a
new option <tt>orderedThreadPoolExecutor</tt> you can configure it to false to
revert back to unordered if needed. If using SSL etc. then ordered is required to be used.</li><li>The
default value of the <tt>delay</tt> option on <a shape="rect" href="timer.html"
title="Timer">Timer</a> has been changed from <tt>0</tt> to <tt>1000</tt></li><li>The
default value 
 of the <tt>convertLFtoCR</tt> option of the <a shape="rect" href="hl7.html"
title="HL7">HL7</a> MLLP codec has been changed from <tt>true</tt> to
<tt>false</tt>. Likewise, the <a shape="rect" href="hl7.html" title="HL7">HL7</a>
DataFormat and TypeConverter do not perform this conversion anymore.</li><li>The
<a shape="rect" href="simple.html" title="Simple">Simple</a> language has limited
its support for the escape character to only new line, carriage return and tab characters.
This makes it easier to use back-slash characters in the <a shape="rect" href="simple.html"
title="Simple">Simple</a> language without double escaping etc.</li><li><tt>camel-netty</tt>
now requires <tt>commons-pool</tt> as dependency.</li><li>The <tt>maximumQueueSize</tt>
of <a shape="rect" class="external-link" href="http://camel.apache.org/threading-model.html">Thread
Pools</a> and <a shape="rect" class="external-link" href="http://camel.apache.org/threading-model.html">Thread
Pool Profiles</a> with 
 values 0 or negative now means disable the worker queue, and use direct-handover. If you
want an unbounded queue size, then set the <tt>maximumQueueSize</tt> to <tt>Integer.MAX_VALUE</tt>
which was what the previous code did.</li><li>Custom assigned id's on Camel <a
shape="rect" href="routes.html" title="Routes">Routes</a> is now validated on starting
the routes, that they must be unique within the same CamelContext.</li><li><tt>camel-blueprint</tt>
now requires Apache Aries 1.0, and OSGi 4.3.0.</li><li>Removed @deprecated classes
form <tt>camel-spring</tt> in the <tt>org.apache.camel.component</tt>
package which was causing split-package issue with OSGi. Component authors who are using these
@deprecated classes, should migrate to use equivalent classes from <tt>camel-core</tt>
in the same package.</li><li>The default Spring version is upgraded from 3.0.7
to 3.1.3 out of the box.</li><li>Camel now validates <a shape="rect" href="seda.html"
title="SEDA">SEDA</a> and <a shape=
 "rect" href="vm.html" title="VM">VM</a> endpoints using same queue name, that if
any queue size is in use, that size must match. As well Camel logs at INFO level when starting
up the queues and the sizes. This allows end users to easily spot any issues if mistakenly
using different queue sizes for the same queue names.</li></ul>
+<ul><li>Spring 3.0.x support is @deprecated and some of the camel-spring components
require Spring 3.1 onwards.</li><li>Apache Camel Karaf features now uses Spring
version range "[3.1,4)" as Spring 3.1 is now required as minimum Spring version.</li><li><tt>camel-mina2</tt>
now uses <tt>OrderedThreadPoolExecutor</tt> by default. There is a new option
<tt>orderedThreadPoolExecutor</tt> you can configure it to <tt>false</tt>
to revert back to unordered if needed. If using SSL etc. then ordered is required to be used.</li><li><tt>camel-netty</tt>
now uses <tt>OrderedMemoryAwareThreadPoolExecutor</tt> by default. There is a
new option <tt>orderedThreadPoolExecutor</tt> you can configure it to false to
revert back to unordered if needed. If using SSL etc. then ordered is required to be used.</li><li>The
default value of the <tt>delay</tt> option on <a shape="rect" href="timer.html"
title="Timer">Timer</a> has been changed from <tt>0</tt> to <tt>1000</tt></li><li>The
default value 
 of the <tt>convertLFtoCR</tt> option of the <a shape="rect" href="hl7.html"
title="HL7">HL7</a> MLLP codec has been changed from <tt>true</tt> to
<tt>false</tt>. Likewise, the <a shape="rect" href="hl7.html" title="HL7">HL7</a>
DataFormat and TypeConverter do not perform this conversion anymore.</li><li>The
<a shape="rect" href="simple.html" title="Simple">Simple</a> language has limited
its support for the escape character to only new line, carriage return and tab characters.
This makes it easier to use back-slash characters in the <a shape="rect" href="simple.html"
title="Simple">Simple</a> language without double escaping etc.</li><li><tt>camel-netty</tt>
now requires <tt>commons-pool</tt> as dependency.</li><li>The <tt>maximumQueueSize</tt>
of <a shape="rect" class="external-link" href="http://camel.apache.org/threading-model.html">Thread
Pools</a> and <a shape="rect" class="external-link" href="http://camel.apache.org/threading-model.html">Thread
Pool Profiles</a> with 
 values 0 or negative now means disable the worker queue, and use direct-handover. If you
want an unbounded queue size, then set the <tt>maximumQueueSize</tt> to <tt>Integer.MAX_VALUE</tt>
which was what the previous code did.</li><li>Custom assigned id's on Camel <a
shape="rect" href="routes.html" title="Routes">Routes</a> is now validated on starting
the routes, that they must be unique within the same CamelContext.</li><li><tt>camel-blueprint</tt>
now requires Apache Aries 1.0, and OSGi 4.3.0.</li><li>Removed @deprecated classes
form <tt>camel-spring</tt> in the <tt>org.apache.camel.component</tt>
package which was causing split-package issue with OSGi. Component authors who are using these
@deprecated classes, should migrate to use equivalent classes from <tt>camel-core</tt>
in the same package.</li><li>The default Spring version is upgraded from 3.0.7
to 3.1.3 out of the box.</li><li>Camel now validates <a shape="rect" href="seda.html"
title="SEDA">SEDA</a> and <a shape=
 "rect" href="vm.html" title="VM">VM</a> endpoints using same queue name, that if
any queue size is in use, that size must match. As well Camel logs at INFO level when starting
up the queues and the sizes. This allows end users to easily spot any issues if mistakenly
using different queue sizes for the same queue names.</li><li>The <a shape="rect"
href="zookeeper.html" title="Zookeeper">Zookeeper component</a> <tt>awaitExistence</tt>
option has been marked as <tt>@Deprecated</tt> and is removed from it's documentation
as the usage of this option had no effect anyway.</li></ul>
 
 
 <h2><a shape="rect" name="Camel2.11.0Release-Notice"></a>Notice</h2>



Mime
View raw message