Modified: websites/production/camel/content/camel-210-release.html
==============================================================================
--- websites/production/camel/content/camel-210-release.html (original)
+++ websites/production/camel/content/camel-210-release.html Sun Mar 9
23:18:55 2014
@@ -86,197 +86,30 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h1
id="Camel2.1.0Release-Camel2.1.0release">Camel 2.1.0 release</h1>
-
-<div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="image-wrap" style=""><img
src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png";
style="border: 0px solid black"></span></p></div>
-<div style="min-height:200px"></div>
-
-<h2 id="Camel2.1.0Release-NewandNoteworthy">New and Noteworthy</h2>
-
-<p>Welcome to the 2.1.0 release which approx 303 issues resolved (new
features, improvements and bug fixes such as...)</p>
-
-<ul><li>Pluggable API for Management allowing 3rd party to manage Camel.
- <ul><li>Use <code>org.apache.camel.spi.ManagementStrategy</code> to
plugin 3rd party adapter</li><li>Fine grained events notifications is now being
emitted using <code>org.apache.camel.spi.EventNotifier</code></li><li>Events
being fired can be created using a pluggable factory using
<code>org.apache.camel.spi.EventFactory</code></li><li>Camel now supports using
multiple <code>org.apache.camel.spi.LifecycleStrategy</code> strategies, that
also allows 3rd party to more easily integrate into Camel.</li></ul>
- </li><li>Overhaul of default <a shape="rect" href="camel-jmx.html">JMX
management</a> in Camel to be much improved with more attributes, mbeans,
operations, statistics, and route timing working as well.
- <ul><li>And yes you can now start/stop routes and individual consumers
and producers</li><li>And some special processors such as <a shape="rect"
href="delayer.html">Delayer</a> and <a shape="rect"
href="throttler.html">Throttler</a> can be managed to change their
delay/throttle values</li><li>You can dynamic manage <a shape="rect"
href="tracer.html">tracing</a> even for already running applications</li><li><a
shape="rect" href="error-handling-in-camel.html">Error handling in Camel</a> is
now also manageable so you for example can change the redelivery
policies.</li><li><a shape="rect" href="jms.html">JMS</a> consumers being
restarted will pickup any configuration changes on JMS endpoints such as
changing <code>concurrentConsumers</code>. And yes its fully managed using
JMX.</li><li>Number of inflight exchanges per consumer, route and totally per
camel context.</li><li>And much more...</li></ul>
- </li><li>Improved <a shape="rect" href="irc.html">Irc</a>, <a
shape="rect" href="xmpp.html">Xmpp</a>, <a shape="rect"
href="mina.html">Mina</a>, <a shape="rect" href="cxf.html">CXF</a> and <a
shape="rect" href="freemarker.html">FreeMarker</a> components with much thanks
to the Camel community</li><li>Added classLoader set and get method in the
CamelContext to make Camel work better in the Container.</li><li>Introduced
camel-spring-osgi bundle which is merged from camel-spring and camel-osgi
bundle to avoid the issue of installing upper bundles in a wrong
order.</li><li>Now Camel Karaf features are validated with the Karaf
plugin.</li><li><a shape="rect" href="cxf.html">camel-cxf</a> beans component
supports JAXWS beans.</li><li>camel-cxf MTOM attachment supports in Payload
mode.</li><li>Fixed the Null message will cause camel converter stop working
issue.</li><li>camel-cxf endpoint no longer requires the "serviceClass" option
or Service Endpoint Interface (SEI) in Payload mode.
0; It means only WSDL is needed but the intended port and service name in the
WSDL must be provided for the camel-cxf endpoint.</li><li><a shape="rect"
href="velocity.html">Velocity</a> component supports to take the Velocity
configuration by using propertiesFile option.</li><li><a shape="rect"
href="splitter.html">Splitter</a> and <a shape="rect"
href="multicast.html">Multicast</a> EIP patterns now support the option
<code>stopOnException</code> to stop continue processing at first exception
occurred. See their documentation for more details.</li><li><a shape="rect"
href="error-handling-in-camel.html">Error handlers</a> is restricted to be
configured on camel context and/or routes only.</li><li>Camel is now more
robust and fault tolerant when shutting down.</li><li>Fixed a race condition
when shutting down Camel with <a shape="rect" href="jms.html">JMS</a> consumers
that under some circumstances caused it to appear to hang</li><li>Added
pluggable <code>org.apache.camel.spi.Inflight
Repository</code> with a basic implementation that can help with graceful
shutdown as you can now see how many exchanges are currently in
progress.</li><li><a shape="rect" href="jms.html">JmsEndpoint</a> is now
singleton</li><li>Individual routes can be <a shape="rect"
href="configuring-route-startup-ordering-and-autostartup.html">pre configured
to not auto startup</a> when Camel starts: <code>autoStartup=false</code> in
XML DSL and <code>noAutoStartup()</code> in Java DSL.</li><li>Camel is more
robust on startup as route inputs are deferred to be started at the very end,
ensuring all routes services have been pre started and thus ready when
consumers is started.</li><li>Improved unit test coverage, now having more than
4200 unit tests in total.</li><li>Fixed <code>ConsumerTemplate</code> not
working when it was dependency injected with <code>@EndpointInjected</code> in
a <a shape="rect" href="bean.html">Bean</a>.</li><li>Using IBM special JMS
headers now work when sending messages
to IBM WebSphere MQ. IBM special headers uses this prefix:
<code>JMS_IBM_</code>. In fact it works with any
<code>JMS_<vendor>_</code> header.</li><li>The <a shape="rect"
href="configuring-route-startup-ordering-and-autostartup.html">ordering of
which routes should be started</a> can now be configured by the
<code>startupOrder</code> attribute which defines a number. Lowest number is
started first.</li><li>And <code>autoStartup</code> is also supported on <a
shape="rect" href="camelcontext.html">CamelContext</a> itself where it replaces
the <code>shouldStartContext</code> option, which have been
removed.</li><li>Camel now checks on startup if multiple routes uses the
<strong>same</strong> endpoint as inputs, if so it fails to start. This
prevents starting Camel if you have routes with e.g. copy/paste typos. Only <a
shape="rect" href="jms.html">JMS</a> and <a shape="rect"
href="mina.html">Mina</a> support multiple routes to consume from
<strong>same</strong> endpoint. The <code
>MultipeConsumersSupport</code> interface can be optionally implemented by the
>endpoint to control this behavior.</li><li>The <a shape="rect"
>href="file2.html">File</a> component handles renaming and deleting files on
>Windows better as Windows could block files. Also Antivirus software could
>causes files to be blocked.</li><li>Fixed issues using
><code>tempPrefix</code> option with the <a shape="rect"
>href="file2.html">File</a> in case of clashes with existing files. The same
>goes for the <code>localWorkDirectory</code> option on the <a shape="rect"
>href="ftp2.html">FTP</a> component which could have a similar
>issue.</li><li>Optimized <a shape="rect" href="xpath.html">XPath</a> to allow
>thread safe concurrency which greatly reduces contention.</li><li>Camel works
>better with Google App Engine</li><li>The <a shape="rect"
>href="bean.html">Bean</a> component is better at choosing the best method. If
>given a method name it will only pick among methods with such a
>name.</li><li>The <a sha
pe="rect" href="bean.html">Bean</a> component is now also more strict as it
<strong>must</strong> be able to convert to all the parameter types. Was to
lenient before by passing in <code>null</code> instead, when conversion was not
successful.</li><li>The <a shape="rect" href="bean.html">Bean</a> component now
works with Spring @Transactional annotations where it uses CGLIB enhanced
classes.</li><li>Fixed an issue with setting global error handling in Spring
XML not always working</li><li>Camel <a shape="rect"
href="dead-letter-channel.html">adds properties</a> to <a shape="rect"
href="exchange.html">Exchange</a> when sending to endpoints. This is useable
with <a shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a>
where we can use this to know which <a shape="rect"
href="endpoint.html">Endpoint</a> failed.</li><li>Improved file operations on
Windows platform to retry in case of issues.</li><li>Fixed issue with
<code>replyTo</code> option on <a shape="rect" href="jms
.html">JMS</a> consumers which wasn't working.</li><li>Fixed issue with using
<camel:proxy> not working</li><li>Improved
<code><camel:proxy></code> so its easier to work with out of the box. It
leverages Camels type converter mechanism to adapt to the interface. Also
proxied methods with a single parameter turns that parameter value into the
message body.</li><li>Added document for using <a shape="rect"
href="using-camelproxy.html">Camel proxy</a>.</li><li>Improved
<code>enrich</code> and <code>pollEnrich</code> with reference lookup of
endpoints and aggregation strategy.</li><li>Added <code>markRollbackOnly</code>
attribute on <code><rollback></code> to only mark the <a shape="rect"
href="exchange.html">Exchange</a> for rollback. This allows you to set a custom
reply message. Previously a <code>RollbackExchangeException</code> was always
set which causes Camel to thrown an exception to the client. This also works
with <code>transacted</code> routes as well.</li><l
i>Camel now logs on shutdown whether there was in flight exchanges or not. All
together we are getting closer to having graceful shutdown supported in
Camel.</li><li><code>@Bean</code> is now easier to use at you define
<code>ref</code> and <code>method</code> instead of one combined
value.</li><li>Introduced <code>routeId</code> in the Java DSL to set the id of
the route. Prefer to use this over <code>id</code>.</li><li>Introduced <a
shape="rect" href="routepolicy.html">RoutePolicy</a> allowing to automatic and
dynamically controlling routes at runtime.</li><li>Supplied
<code>ThrottlingRoutePolicy</code> out of the box for dynamic throttling route
consumers using metrics based on the current number of inflight
exchanges.</li><li><a shape="rect" href="data-format.html">Data Format</a> is
now resolved just as <a shape="rect" href="components.html">Components</a> and
<a shape="rect" href="languages.html">Languages</a> by looking for magic file
under <code>META-INF/services/org/apache/
camel/dataformat/</code>.</li><li>The <a shape="rect"
href="http.html">HTTP</a> component now also supports using NTLM
authentication</li><li><a shape="rect" href="exception-clause.html">Exception
Clause</a> improved to better select the best <code>onException</code> to use.
Now a direct match will <strong>always</strong> be used in case one existed
anywhere in the caused exception hierarchy. This avoid Camel eagerly selecting
a too generic such as <code>onException(Exception.class)</code> when a direct
match existed.</li><li><a shape="rect" href="ftp2.html">FTP</a> can now have
its <code>FTPClient</code> and <code>FTPClientConfig</code> configured using
URI parameters. Can for example be used to set a timeout on the
<code>FTPClient</code>.</li><li><a shape="rect" href="ftp2.html">FTP</a> is now
more robust when writing files where it will reconnect the connect in case of
problems.</li><li>Added support in camel-core for non blocking <a shape="rect"
href="request-reply.html">Request
Reply</a> using <a shape="rect" href="toasync.html">ToAsync</a>.</li><li><a
shape="rect" href="jetty.html">Jetty</a> HTTP producer supports non blocking <a
shape="rect" href="request-reply.html">Request Reply</a>. See more at <a
shape="rect" href="toasync.html">ToAsync</a> and the <a shape="rect"
href="http-async-example.html">HTTP Async
Example</a>.</li><li><code>HttpOperationFailedException</code> now uses pure
Java types so it can safely be transported over network without being dependent
on 3rd part .jars.</li><li>Improvements to <a shape="rect"
href="tracer.html">Tracer</a> to let it be more fine grained when used with <a
shape="rect" href="aggregator.html">Aggregator</a>, <a shape="rect"
href="splitter.html">Splitter</a> etc. who has sub routes. It now also outputs
correct doTry .. doCatch .. doFinally and onException etc.</li><li>Added
<code>adviceWith(RouteBuilder)</code> to <code>RouteDefinition</code> which
allows you to advice any existing route with a route builder wher
e you can define interceptors etc. This is useable for testing so you can
write tests based on existing routes and advice them with interceptors so you
can detour messages and simulate errors etc.</li><li><a shape="rect"
href="timer.html">Timer</a> and <a shape="rect" href="quartz.html">Quartz</a>
now logs Exchanges that failed with an exception at ERROR level to help
identify the problem.</li><li><a shape="rect"
href="tutorial-for-camel-on-google-app-engine.html">Google App Engine
supported</a> excellent work by our new committer Martin
Krasser.</li><li>Improved <a shape="rect" href="cxf.html">CXF</a> producer in
<code>POJO</code> mode to use the POJO body without having to wrap it in a
<code>java.util.List</code> which allows for easier usage. See for example the
<a shape="rect" href="cxf-async-example.html">CXF Async
Example</a>.</li><li>Added option <code>testConnectionOnStartup</code> to <a
shape="rect" href="jms.html">JMS</a> to test connection on startup. The goal is
to ensur
es that when Camel is started all the JMS consumers have a valid connection to
the JMS broker. However if a connection cannot be established then Camel throws
an exception on startup.</li><li><a shape="rect"
href="dead-letter-channel.html">Dead Letter Channel</a> is validating its
<code>deadLetterUri</code> on startup to prevent failing at
runtime.</li><li>Failing to create routes is now reported with a more precise
error message which pinpoints which route and what part of the route is causing
the problem.</li><li>Fixed issue with transacted routes mixed with Camel error
handling doing redelivery from the beginning of the route and not only at the
failed node in the route path.</li><li>Fixed issue with using <a shape="rect"
href="bam.html">BAM</a> with Hibernate.</li><li>Options to the
<code>java.sql.Statement</code> can be set from the URI in the <a shape="rect"
href="jdbc.html">JDBC</a> component. Can be used to set maxRows
etc.</li><li>Added documentation for <a shape="rect" hre
f="nmr.html">NMR</a> and <a shape="rect"
href="quickfix.html">Quickfix</a>.</li><li>Fixed issues with <a shape="rect"
href="mail.html">Mail</a> and having multiple endpoints defined with different
recipients could cause Camel to use the recipients from the last defined
endpoint only.</li><li>Improved <a shape="rect" href="mail.html">Mail</a> to
better recover from network failure on subsequent polls</li><li>Improved <a
shape="rect" href="tracer.html">Tracer</a> to output route id</li><li>Fixed a
potential 2gb file copy limit using NIO when doing
from("file:xxx").XXXX.to("file:yyy") routing.</li><li>Upgraded and fixed <a
shape="rect" href="el.html">EL</a> to work with OSGi containers.</li></ul>
-
-
-<h3 id="Camel2.1.0Release-New">New <a shape="rect"
href="enterprise-integration-patterns.html">Enterprise Integration
Patterns</a></h3>
-
-<ul><li><a shape="rect" href="sampling.html">Sampling</a> A sampling throttler
allowing you to extract a sample of exchanges from the traffic through a
route.</li></ul>
-
-
-<h3 id="Camel2.1.0Release-New.1">New <a shape="rect"
href="components.html">Components</a></h3>
-
-<ul><li><a shape="rect" href="printer.html">camel-printer</a></li><li><a
shape="rect" href="cache.html">camel-cache</a></li><li><a shape="rect"
href="snmp.html">camel-snmp</a></li><li><a shape="rect"
href="javaspace.html">camel-javaspace</a></li><li><a shape="rect"
href="gae.html">camel-gae</a></li><li><a shape="rect"
href="quickfix.html">camel-quickfix</a></li></ul>
-
-
-
-<h3 id="Camel2.1.0Release-NewDSL">New DSL</h3>
-
-<ul><li><a shape="rect"
href="sampling.html"><code>sample</code></a></li><li><code>markRollbackOnly</code></li><li><code>routeId</code></li><li><a
shape="rect"
href="toasync.html"><code>toAsync</code></a></li><li><code>autoStartup</code></li><li><code>startupOrder</code></li></ul>
-
-
-
-<h3 id="Camel2.1.0Release-NewAnnotations">New Annotations</h3>
-
-<h3 id="Camel2.1.0Release-NewDataFormats">New <a shape="rect"
href="data-format.html">Data Formats</a></h3>
-
-<ul><li>Camel-bindy <a shape="rect" href="bindy.html">bindy</a> includes
important new features like :
- <ul><li>Required (@DataField) to check mandatory field</li><li>Position
(@DataField and @KeyValuePairField) when the CSV/FIX message to be generate
contain fields which are placed at a different position then those used to
parse it</li><li>Section which allow to define the class containing by example
the header, body or footer section</li><li>OneToMany which allow to Read a FIX
message containing repetitive groups (= group of tags/keys) and Generate a CSV
with repetitive data</li></ul>
- </li></ul>
-
-
-<h3 id="Camel2.1.0Release-New.2">New <a shape="rect"
href="languages.html">Languages</a></h3>
-
-<h3 id="Camel2.1.0Release-New.3">New <a shape="rect"
href="examples.html">Examples</a></h3>
-
-<ul><li><a shape="rect"
href="management-example.html">camel-example-management</a></li><li><a
shape="rect"
href="route-throttling-example.html">camel-example-route-throttling</a></li><li><a
shape="rect"
href="http-async-example.html">camel-example-http-async</a></li><li><a
shape="rect" href="cxf-async-example.html">camel-example-cxf-async</a></li></ul>
-
-
-<h2 id="Camel2.1.0Release-APIbreaking">API breaking</h2>
-
-<h3 id="Camel2.1.0Release-DSLchanges">DSL changes</h3>
-
-<p>In the Java DSL the <code>.errorHandler</code> is now restricted to be
configured on camel context and/or routes only. That means for configuring on
routes you have to set it directly after the <code>.from</code> DSL.</p>
-
-<p>In Spring DSL the <code>errorHandlerRef</code> attribute is now only
visible on the <code><camelContext></code> and <code><route></code>
XML tags.</p>
-
-<h3 id="Camel2.1.0Release-New.jardependencies">New .jar dependencies</h3>
-
-<p>camel-core now depends on commons-management.jar to facilitate the new
overhauled management.<br clear="none">
-This project is hosted at <a shape="rect" class="external-link"
href="http://commonman.fusesource.org/"; rel="nofollow">FuseForge</a></p>
-
-<p>This .jar can be retrieved from the maven central repo at: <a shape="rect"
class="external-link"
href="http://repo1.maven.org/maven2/org/fusesource/commonman/commons-management/1.0/";
rel="nofollow">http://repo1.maven.org/maven2/org/fusesource/commonman/commons-management/1.0/</a><br
clear="none">
-The maven dependency details are:</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[
- <groupId>org.fusesource.commonman</groupId>
+<div class="wiki-content maincontent"><h1
id="Camel2.1.0Release-Camel2.1.0release">Camel 2.1.0 release</h1><div
style="padding-right:20px;float:left;margin-left:-20px;">
+<p><span class="image-wrap" style=""><img
src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png";
style="border: 0px solid black"></span></p></div><div
style="min-height:200px"></div><h2 id="Camel2.1.0Release-NewandNoteworthy">New
and Noteworthy</h2><p>Welcome to the 2.1.0 release which approx 303 issues
resolved (new features, improvements and bug fixes such
as...)</p><ul><li>Pluggable API for Management allowing 3rd party to manage
Camel.<ul><li>Use <code>org.apache.camel.spi.ManagementStrategy</code> to
plugin 3rd party adapter</li><li>Fine grained events notifications is now being
emitted using <code>org.apache.camel.spi.EventNotifier</code></li><li>Events
being fired can be created using a pluggable factory using
<code>org.apache.camel.spi.EventFactory</code></li><li>Camel now supports using
multiple <code>org.apache.camel.spi.LifecycleStrategy</code> strategies, that
also allows 3rd party to more easily integrate into
Camel.</li></ul></li><li>Overhaul of default
<a shape="rect" href="camel-jmx.html">JMX management</a> in Camel to be much
improved with more attributes, mbeans, operations, statistics, and route timing
working as well.<ul><li>And yes you can now start/stop routes and individual
consumers and producers</li><li>And some special processors such as <a
shape="rect" href="delayer.html">Delayer</a> and <a shape="rect"
href="throttler.html">Throttler</a> can be managed to change their
delay/throttle values</li><li>You can dynamic manage <a shape="rect"
href="tracer.html">tracing</a> even for already running applications</li><li><a
shape="rect" href="error-handling-in-camel.html">Error handling in Camel</a> is
now also manageable so you for example can change the redelivery
policies.</li><li><a shape="rect" href="jms.html">JMS</a> consumers being
restarted will pickup any configuration changes on JMS endpoints such as
changing <code>concurrentConsumers</code>. And yes its fully managed using
JMX.</li><li>Number of inflight exchanges p
er consumer, route and totally per camel context.</li><li>And much
more...</li></ul></li><li>Improved <a shape="rect" href="irc.html">IRC</a>, <a
shape="rect" href="xmpp.html">XMPP</a>, <a shape="rect"
href="mina.html">MINA</a>, <a shape="rect" href="cxf.html">CXF</a> and <a
shape="rect" href="freemarker.html">FreeMarker</a> components with much thanks
to the Camel community</li><li>Added classLoader set and get method in the
CamelContext to make Camel work better in the Container.</li><li>Introduced
camel-spring-osgi bundle which is merged from camel-spring and camel-osgi
bundle to avoid the issue of installing upper bundles in a wrong
order.</li><li>Now Camel Karaf features are validated with the Karaf
plugin.</li><li><a shape="rect" href="cxf.html">camel-cxf</a> beans component
supports JAXWS beans.</li><li>camel-cxf MTOM attachment supports in Payload
mode.</li><li>Fixed the Null message will cause camel converter stop working
issue.</li><li>camel-cxf endpoint no longer requires
the "serviceClass" option or Service Endpoint Interface (SEI) in Payload
mode.  It means only WSDL is needed but the intended port and service name
in the WSDL must be provided for the camel-cxf endpoint.</li><li><a
shape="rect" href="velocity.html">Velocity</a> component supports to take the
Velocity configuration by using propertiesFile option.</li><li><a shape="rect"
href="splitter.html">Splitter</a> and <a shape="rect"
href="multicast.html">Multicast</a> EIP patterns now support the option
<code>stopOnException</code> to stop continue processing at first exception
occurred. See their documentation for more details.</li><li><a shape="rect"
href="error-handling-in-camel.html">Error handlers</a> is restricted to be
configured on camel context and/or routes only.</li><li>Camel is now more
robust and fault tolerant when shutting down.</li><li>Fixed a race condition
when shutting down Camel with <a shape="rect" href="jms.html">JMS</a> consumers
that under some circumstances caus
ed it to appear to hang</li><li>Added pluggable
<code>org.apache.camel.spi.InflightRepository</code> with a basic
implementation that can help with graceful shutdown as you can now see how many
exchanges are currently in progress.</li><li><a shape="rect"
href="jms.html">JmsEndpoint</a> is now singleton</li><li>Individual routes can
be <a shape="rect"
href="configuring-route-startup-ordering-and-autostartup.html">pre configured
to not auto startup</a> when Camel starts: <code>autoStartup=false</code> in
XML DSL and <code>noAutoStartup()</code> in Java DSL.</li><li>Camel is more
robust on startup as route inputs are deferred to be started at the very end,
ensuring all routes services have been pre started and thus ready when
consumers is started.</li><li>Improved unit test coverage, now having more than
4200 unit tests in total.</li><li>Fixed <code>ConsumerTemplate</code> not
working when it was dependency injected with <code>@EndpointInjected</code> in
a <a shape="rect" href="bean.ht
ml">Bean</a>.</li><li>Using IBM special JMS headers now work when sending
messages to IBM WebSphere MQ. IBM special headers uses this prefix:
<code>JMS_IBM_</code>. In fact it works with any
<code>JMS_<vendor>_</code> header.</li><li>The <a shape="rect"
href="configuring-route-startup-ordering-and-autostartup.html">ordering of
which routes should be started</a> can now be configured by the
<code>startupOrder</code> attribute which defines a number. Lowest number is
started first.</li><li>And <code>autoStartup</code> is also supported on <a
shape="rect" href="camelcontext.html">CamelContext</a> itself where it replaces
the <code>shouldStartContext</code> option, which have been
removed.</li><li>Camel now checks on startup if multiple routes uses the
<strong>same</strong> endpoint as inputs, if so it fails to start. This
prevents starting Camel if you have routes with e.g. copy/paste typos. Only <a
shape="rect" href="jms.html">JMS</a> and <a shape="rect"
href="mina.html">MINA</a
> support multiple routes to consume from <strong>same</strong> endpoint. The
> <code>MultipeConsumersSupport</code> interface can be optionally implemented
> by the endpoint to control this behavior.</li><li>The <a shape="rect"
> href="file2.html">File</a> component handles renaming and deleting files on
> Windows better as Windows could block files. Also Antivirus software could
> causes files to be blocked.</li><li>Fixed issues using
> <code>tempPrefix</code> option with the <a shape="rect"
> href="file2.html">File</a> in case of clashes with existing files. The same
> goes for the <code>localWorkDirectory</code> option on the <a shape="rect"
> href="ftp2.html">FTP</a> component which could have a similar
> issue.</li><li>Optimized <a shape="rect" href="xpath.html">XPath</a> to
> allow thread safe concurrency which greatly reduces
> contention.</li><li>Camel works better with Google App Engine</li><li>The <a
> shape="rect" href="bean.html">Bean</a> component is better at choosing the
> best method. If given
a method name it will only pick among methods with such a name.</li><li>The
<a shape="rect" href="bean.html">Bean</a> component is now also more strict as
it <strong>must</strong> be able to convert to all the parameter types. Was to
lenient before by passing in <code>null</code> instead, when conversion was not
successful.</li><li>The <a shape="rect" href="bean.html">Bean</a> component now
works with Spring @Transactional annotations where it uses CGLIB enhanced
classes.</li><li>Fixed an issue with setting global error handling in Spring
XML not always working</li><li>Camel <a shape="rect"
href="dead-letter-channel.html">adds properties</a> to <a shape="rect"
href="exchange.html">Exchange</a> when sending to endpoints. This is useable
with <a shape="rect" href="dead-letter-channel.html">Dead Letter Channel</a>
where we can use this to know which <a shape="rect"
href="endpoint.html">Endpoint</a> failed.</li><li>Improved file operations on
Windows platform to retry in case of issues
.</li><li>Fixed issue with <code>replyTo</code> option on <a shape="rect"
href="jms.html">JMS</a> consumers which wasn't working.</li><li>Fixed issue
with using <camel:proxy> not working</li><li>Improved
<code><camel:proxy></code> so its easier to work with out of the box. It
leverages Camels type converter mechanism to adapt to the interface. Also
proxied methods with a single parameter turns that parameter value into the
message body.</li><li>Added document for using <a shape="rect"
href="using-camelproxy.html">Camel proxy</a>.</li><li>Improved
<code>enrich</code> and <code>pollEnrich</code> with reference lookup of
endpoints and aggregation strategy.</li><li>Added <code>markRollbackOnly</code>
attribute on <code><rollback></code> to only mark the <a shape="rect"
href="exchange.html">Exchange</a> for rollback. This allows you to set a custom
reply message. Previously a <code>RollbackExchangeException</code> was always
set which causes Camel to thrown an exception
to the client. This also works with <code>transacted</code> routes as
well.</li><li>Camel now logs on shutdown whether there was in flight exchanges
or not. All together we are getting closer to having graceful shutdown
supported in Camel.</li><li><code>@Bean</code> is now easier to use at you
define <code>ref</code> and <code>method</code> instead of one combined
value.</li><li>Introduced <code>routeId</code> in the Java DSL to set the id of
the route. Prefer to use this over <code>id</code>.</li><li>Introduced <a
shape="rect" href="routepolicy.html">RoutePolicy</a> allowing to automatic and
dynamically controlling routes at runtime.</li><li>Supplied
<code>ThrottlingRoutePolicy</code> out of the box for dynamic throttling route
consumers using metrics based on the current number of inflight
exchanges.</li><li><a shape="rect" href="data-format.html">Data Format</a> is
now resolved just as <a shape="rect" href="components.html">Components</a> and
<a shape="rect" href="languages.html
">Languages</a> by looking for magic file under
<code>META-INF/services/org/apache/camel/dataformat/</code>.</li><li>The <a
shape="rect" href="http.html">HTTP</a> component now also supports using NTLM
authentication</li><li><a shape="rect" href="exception-clause.html">Exception
Clause</a> improved to better select the best <code>onException</code> to use.
Now a direct match will <strong>always</strong> be used in case one existed
anywhere in the caused exception hierarchy. This avoid Camel eagerly selecting
a too generic such as <code>onException(Exception.class)</code> when a direct
match existed.</li><li><a shape="rect" href="ftp2.html">FTP</a> can now have
its <code>FTPClient</code> and <code>FTPClientConfig</code> configured using
URI parameters. Can for example be used to set a timeout on the
<code>FTPClient</code>.</li><li><a shape="rect" href="ftp2.html">FTP</a> is now
more robust when writing files where it will reconnect the connect in case of
problems.</li><li>Added suppo
rt in camel-core for non blocking <a shape="rect"
href="request-reply.html">Request Reply</a> using <a shape="rect"
href="toasync.html">ToAsync</a>.</li><li><a shape="rect"
href="jetty.html">Jetty</a> HTTP producer supports non blocking <a shape="rect"
href="request-reply.html">Request Reply</a>. See more at <a shape="rect"
href="toasync.html">ToAsync</a> and the <a shape="rect"
href="http-async-example.html">HTTP Async
Example</a>.</li><li><code>HttpOperationFailedException</code> now uses pure
Java types so it can safely be transported over network without being dependent
on 3rd part .jars.</li><li>Improvements to <a shape="rect"
href="tracer.html">Tracer</a> to let it be more fine grained when used with <a
shape="rect" href="aggregator.html">Aggregator</a>, <a shape="rect"
href="splitter.html">Splitter</a> etc. who has sub routes. It now also outputs
correct doTry .. doCatch .. doFinally and onException etc.</li><li>Added
<code>adviceWith(RouteBuilder)</code> to <code>RouteDefini
tion</code> which allows you to advice any existing route with a route builder
where you can define interceptors etc. This is useable for testing so you can
write tests based on existing routes and advice them with interceptors so you
can detour messages and simulate errors etc.</li><li><a shape="rect"
href="timer.html">Timer</a> and <a shape="rect" href="quartz.html">Quartz</a>
now logs Exchanges that failed with an exception at ERROR level to help
identify the problem.</li><li><a shape="rect"
href="tutorial-for-camel-on-google-app-engine.html">Google App Engine
supported</a> excellent work by our new committer Martin
Krasser.</li><li>Improved <a shape="rect" href="cxf.html">CXF</a> producer in
<code>POJO</code> mode to use the POJO body without having to wrap it in a
<code>java.util.List</code> which allows for easier usage. See for example the
<a shape="rect" href="cxf-async-example.html">CXF Async
Example</a>.</li><li>Added option <code>testConnectionOnStartup</code> to <a
shape
="rect" href="jms.html">JMS</a> to test connection on startup. The goal is to
ensures that when Camel is started all the JMS consumers have a valid
connection to the JMS broker. However if a connection cannot be established
then Camel throws an exception on startup.</li><li><a shape="rect"
href="dead-letter-channel.html">Dead Letter Channel</a> is validating its
<code>deadLetterUri</code> on startup to prevent failing at
runtime.</li><li>Failing to create routes is now reported with a more precise
error message which pinpoints which route and what part of the route is causing
the problem.</li><li>Fixed issue with transacted routes mixed with Camel error
handling doing redelivery from the beginning of the route and not only at the
failed node in the route path.</li><li>Fixed issue with using <a shape="rect"
href="bam.html">BAM</a> with Hibernate.</li><li>Options to the
<code>java.sql.Statement</code> can be set from the URI in the <a shape="rect"
href="jdbc.html">JDBC</a> component.
Can be used to set maxRows etc.</li><li>Added documentation for <a
shape="rect" href="nmr.html">NMR</a> and <a shape="rect"
href="quickfix.html">Quickfix</a>.</li><li>Fixed issues with <a shape="rect"
href="mail.html">Mail</a> and having multiple endpoints defined with different
recipients could cause Camel to use the recipients from the last defined
endpoint only.</li><li>Improved <a shape="rect" href="mail.html">Mail</a> to
better recover from network failure on subsequent polls</li><li>Improved <a
shape="rect" href="tracer.html">Tracer</a> to output route id</li><li>Fixed a
potential 2gb file copy limit using NIO when doing
from("file:xxx").XXXX.to("file:yyy") routing.</li><li>Upgraded and fixed <a
shape="rect" href="el.html">EL</a> to work with OSGi containers.</li></ul><h3
id="Camel2.1.0Release-New">New <a shape="rect"
href="enterprise-integration-patterns.html">Enterprise Integration
Patterns</a></h3><ul><li><a shape="rect" href="sampling.html">Sampling</a> A
sampling throttle
r allowing you to extract a sample of exchanges from the traffic through a
route.</li></ul><h3 id="Camel2.1.0Release-New.1">New <a shape="rect"
href="components.html">Components</a></h3><ul><li><a shape="rect"
href="printer.html">camel-printer</a></li><li><a shape="rect"
href="cache.html">camel-cache</a></li><li><a shape="rect"
href="snmp.html">camel-snmp</a></li><li><a shape="rect"
href="javaspace.html">camel-javaspace</a></li><li><a shape="rect"
href="gae.html">camel-gae</a></li><li><a shape="rect"
href="quickfix.html">camel-quickfix</a></li></ul><h3
id="Camel2.1.0Release-NewDSL">New DSL</h3><ul><li><a shape="rect"
href="sampling.html"><code>sample</code></a></li><li><code>markRollbackOnly</code></li><li><code>routeId</code></li><li><a
shape="rect"
href="toasync.html"><code>toAsync</code></a></li><li><code>autoStartup</code></li><li><code>startupOrder</code></li></ul><h3
id="Camel2.1.0Release-NewAnnotations">New Annotations</h3><h3
id="Camel2.1.0Release-NewDataFormats">New <a shap
e="rect" href="data-format.html">Data Formats</a></h3><ul><li>Camel-bindy <a
shape="rect" href="bindy.html">Bindy</a> includes important new features like
:<ul><li>Required (@DataField) to check mandatory field</li><li>Position
(@DataField and @KeyValuePairField) when the CSV/FIX message to be generate
contain fields which are placed at a different position then those used to
parse it</li><li>Section which allow to define the class containing by example
the header, body or footer section</li><li>OneToMany which allow to Read a FIX
message containing repetitive groups (= group of tags/keys) and Generate a CSV
with repetitive data</li></ul></li></ul><h3 id="Camel2.1.0Release-New.2">New <a
shape="rect" href="languages.html">Languages</a></h3><h3
id="Camel2.1.0Release-New.3">New <a shape="rect"
href="examples.html">Examples</a></h3><ul><li><a shape="rect"
href="management-example.html">camel-example-management</a></li><li><a
shape="rect" href="route-throttling-example.html">camel-exampl
e-route-throttling</a></li><li><a shape="rect"
href="http-async-example.html">camel-example-http-async</a></li><li><a
shape="rect"
href="cxf-async-example.html">camel-example-cxf-async</a></li></ul><h2
id="Camel2.1.0Release-APIbreaking">API breaking</h2><h3
id="Camel2.1.0Release-DSLchanges">DSL changes</h3><p>In the Java DSL the
<code>.errorHandler</code> is now restricted to be configured on camel context
and/or routes only. That means for configuring on routes you have to set it
directly after the <code>.from</code> DSL.</p><p>In Spring DSL the
<code>errorHandlerRef</code> attribute is now only visible on the
<code><camelContext></code> and <code><route></code> XML
tags.</p><h3 id="Camel2.1.0Release-New.jardependencies">New .jar
dependencies</h3><p>camel-core now depends on commons-management.jar to
facilitate the new overhauled management.<br clear="none"> This project is
hosted at <a shape="rect" class="external-link"
href="http://commonman.fusesource.org/"; rel="nofo
llow">FuseForge</a></p><p>This .jar can be retrieved from the maven central
repo at: <a shape="rect" class="external-link"
href="http://repo1.maven.org/maven2/org/fusesource/commonman/commons-management/1.0/";
rel="nofollow">http://repo1.maven.org/maven2/org/fusesource/commonman/commons-management/1.0/</a><br
clear="none"> The maven dependency details are:</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[
<groupId>org.fusesource.commonman</groupId>
<artifactId>commons-management</artifactId>
<version>1.0</version>
]]></script>
-</div></div>
-
-<h3 id="Camel2.1.0Release-DataFormatresolution">DataFormat resolution</h3>
-<p>Data formats is now resolved just as components and languages etc. making
it consistent. If you have your own custom data formats you need to create the
magic file under <code>META-INF/services/org/apache/camel/dataformat</code>
which is a file with the data format name. See for example
<code>camel-jackson</code> for an example how to do that.</p>
-
-<h3 id="Camel2.1.0Release-camel-http">camel-http</h3>
-<p><code>HttpOperationFailedException</code> has been changed.</p>
-
-<h3 id="Camel2.1.0Release-CoreAPI">Core API</h3>
-
-<h4 id="Camel2.1.0Release-CamelContext">CamelContext</h4>
-
-<p>CamelContext have renamed the method <code>getLifecycleStrategy</code> to
<code>getLifecycleStrategies</code> and now returns a List.</p>
-
-<h4 id="Camel2.1.0Release-Exchange">Exchange</h4>
-
-<p>The exchange id has been changed to use the <code>java.util.UUID</code>
instead. This allows Camel to run on Google App Engine.</p>
-
-<h4 id="Camel2.1.0Release-Management">Management</h4>
-
-<p>The API in <code>org.apache.camel.spi.ManagementNamingStrategy</code> had
its methods renaming and method signature adjusted to accommodate the big theme
for Camel which was overhaul of management (JMX).</p>
-
-<h4 id="Camel2.1.0Release-SPI">SPI</h4>
-
-<p>The <code>TraceableUnitOfWork</code> has been renamed to
<code>TracedRouteNote</code> which is accessible from
<code>UnitOfWork</code>.</p>
-
-<h4 id="Camel2.1.0Release-DeadLetterChannel">DeadLetterChannel</h4>
-
-<p>The <code>deadLetterUri</code> uri now only accepts a single endpoint which
is prechecked on startup. You cannot any longer using multiple endpoints
separated by comma. That was in fact an internal hidden feature because a
recipient list was used beforehand to produce to the dead letter queue. Adding
the precheck removed the recipient list. You can use <a shape="rect"
href="direct.html">Direct</a> and route to a route which can then use a
recipient list in case you really need this.</p>
-
-<h3 id="Camel2.1.0Release-ClientAPI">Client API</h3>
-
-<h3 id="Camel2.1.0Release-Removedclasses">Removed classes</h3>
-
-<ul><li><code>org.apache.camel.processor.CompositeProcessor</code> was never
used</li><li><code>org.apache.camel.impl.ProducerTemplateProcessor</code> was
never used</li><li><code>org.apache.camel.impl.NoPolicy</code> was never
used</li><li><code>org.apache.camel.spring.handler.LazyLoadingBeanDefinitionParser</code>
was never
used</li><li><code>org.apache.camel.spring.handler.ScriptDefinitionParser</code>
was never
used</li><li><code>org.apache.camel.spring.remoting.SendBeforeInterceptor</code>
was never
used</li><li><code>org.apache.camel.spring.spi.SpringConverters</code> was
never used</li></ul>
-
-
-<h3 id="Camel2.1.0Release-Movedclasses">Moved classes</h3>
-
-<ul><li><code>org.apache.camel.PollingConsumerPollStrategy</code> is moved to
<code>org.apache.camel.spi.PollingConsumerPollStrategy</code></li><li><code>org.apache.camel.impl.scan.PatternBasedPackageScanFilter</code>
is moved to <code>org.apache.camel.spring.PatternBasedPackageScanFilter</code>
in the <strong>camel-spring</strong> jar.</li></ul>
-
-
-<h3 id="Camel2.1.0Release-Removedmethods">Removed methods</h3>
-
-<ul><li><code>getSingletonEndpoints</code> method have been removed from
various classes in the <code>camel-test</code> component.</li></ul>
-
-
-<h3 id="Camel2.1.0Release-RemovedinSpringXML">Removed in Spring XML</h3>
-
-<p>The option <code>shouldStartContext</code> on <camelContext> have
been removed. Its replaced with <code>autoStartup</code> which you can read
more about here <a shape="rect"
href="configuring-route-startup-ordering-and-autostartup.html">Configuring
route startup ordering and autostartup</a>.</p>
-
-<h3 id="Camel2.1.0Release-@Bean">@Bean</h3>
-
-<p>@Bean now uses a <code>ref</code> attribute to refer to the bean name. Also
added a new <code>method</code> attribute to set the method to use
(optional).<br clear="none">
-You need to upgrade your code to use these attributes as the default
<code>value</code> have been removed. We assume only a very few people knew and
uses this @Bean annotation.</p>
-
-<h3 id="Camel2.1.0Release-component"><a shape="rect"
href="direct.html">Direct</a> component</h3>
-<p>The option <code>allowMultipleConsumers</code> has been removed as it did
not make sense to have concurrent consumers on a direct endpoint.</p>
-
-<h2 id="Camel2.1.0Release-KnownIssues">Known Issues</h2>
-
-<p><a shape="rect" href="routing-slip.html">Routing Slip</a> EIP does not
break when Exchange is failed, see <a shape="rect" class="unresolved"
href="#">CAMEL-2245</a>.</p>
-
-<p>Using <transacted/> in Spring XML does not work properly when using
route scoped <onException> and/or <onCompletion>. Using context
scoped works. And the Java DSL does not have this flaw. See <a shape="rect"
class="unresolved" href="#">CAMEL-2336</a>.</p>
-
-<p>When using the <a shape="rect" href="recipient-list.html">Recipient
List</a> together with <a shape="rect" href="mina.html">Mina</a> endpoints
Camel will over time hold on to memory which could lead to OutOfMemoryErrors.
See more at: <a shape="rect" class="external-link"
href="https://issues.apache.org/activemq/browse/CAMEL-2484";>CAMEL-2484</a></p>
-
-<p>See known issues from previous releases.</p>
-
-<h2 id="Camel2.1.0Release-Importantchangestoconsiderwhenupgrading">Important
changes to consider when upgrading</h2>
-
-<h2 id="Camel2.1.0Release-GettingtheDistributions">Getting the
Distributions</h2>
-
-<h3 id="Camel2.1.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.1.0/apache-camel-2.1.0.zip";>apache-camel-2.1.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.1.0/apache-camel-2.1.0.zip.asc";>apache-camel-2.1.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 sh
ape="rect" class="external-link"
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.1.0/apache-camel-2.1.0.tar.gz";>apache-camel-2.1.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.1.0/apache-camel-2.1.0.tar.gz.asc";>apache-camel-2.1.0.tar.gz.asc</a>
</p></td></tr></tbody></table></div>
-
- <div class="aui-message hint shadowed information-macro">
+</div></div><h3 id="Camel2.1.0Release-DataFormatresolution">DataFormat
resolution</h3><p>Data formats is now resolved just as components and languages
etc. making it consistent. If you have your own custom data formats you need to
create the magic file under
<code>META-INF/services/org/apache/camel/dataformat</code> which is a file with
the data format name. See for example <code>camel-jackson</code> for an example
how to do that.</p><h3
id="Camel2.1.0Release-camel-http">camel-http</h3><p><code>HttpOperationFailedException</code>
has been changed.</p><h3 id="Camel2.1.0Release-CoreAPI">Core API</h3><h4
id="Camel2.1.0Release-CamelContext">CamelContext</h4><p>CamelContext have
renamed the method <code>getLifecycleStrategy</code> to
<code>getLifecycleStrategies</code> and now returns a List.</p><h4
id="Camel2.1.0Release-Exchange">Exchange</h4><p>The exchange id has been
changed to use the <code>java.util.UUID</code> instead. This allows Camel to
run on Google App Engine.</p><h4 id="Came
l2.1.0Release-Management">Management</h4><p>The API in
<code>org.apache.camel.spi.ManagementNamingStrategy</code> had its methods
renaming and method signature adjusted to accommodate the big theme for Camel
which was overhaul of management (JMX).</p><h4
id="Camel2.1.0Release-SPI">SPI</h4><p>The <code>TraceableUnitOfWork</code> has
been renamed to <code>TracedRouteNote</code> which is accessible from
<code>UnitOfWork</code>.</p><h4
id="Camel2.1.0Release-DeadLetterChannel">DeadLetterChannel</h4><p>The
<code>deadLetterUri</code> uri now only accepts a single endpoint which is
prechecked on startup. You cannot any longer using multiple endpoints separated
by comma. That was in fact an internal hidden feature because a recipient list
was used beforehand to produce to the dead letter queue. Adding the precheck
removed the recipient list. You can use <a shape="rect"
href="direct.html">Direct</a> and route to a route which can then use a
recipient list in case you really need this.</p><h3
id="Camel2.1.0Release-ClientAPI">Client API</h3><h3
id="Camel2.1.0Release-Removedclasses">Removed
classes</h3><ul><li><code>org.apache.camel.processor.CompositeProcessor</code>
was never
used</li><li><code>org.apache.camel.impl.ProducerTemplateProcessor</code> was
never used</li><li><code>org.apache.camel.impl.NoPolicy</code> was never
used</li><li><code>org.apache.camel.spring.handler.LazyLoadingBeanDefinitionParser</code>
was never
used</li><li><code>org.apache.camel.spring.handler.ScriptDefinitionParser</code>
was never
used</li><li><code>org.apache.camel.spring.remoting.SendBeforeInterceptor</code>
was never
used</li><li><code>org.apache.camel.spring.spi.SpringConverters</code> was
never used</li></ul><h3 id="Camel2.1.0Release-Movedclasses">Moved
classes</h3><ul><li><code>org.apache.camel.PollingConsumerPollStrategy</code>
is moved to
<code>org.apache.camel.spi.PollingConsumerPollStrategy</code></li><li><code>org.apache.camel.impl.scan.PatternBasedPackageScanFilter</code>
is mov
ed to <code>org.apache.camel.spring.PatternBasedPackageScanFilter</code> in
the <strong>camel-spring</strong> jar.</li></ul><h3
id="Camel2.1.0Release-Removedmethods">Removed
methods</h3><ul><li><code>getSingletonEndpoints</code> method have been removed
from various classes in the <code>camel-test</code> component.</li></ul><h3
id="Camel2.1.0Release-RemovedinSpringXML">Removed in Spring XML</h3><p>The
option <code>shouldStartContext</code> on <camelContext> have been
removed. Its replaced with <code>autoStartup</code> which you can read more
about here <a shape="rect"
href="configuring-route-startup-ordering-and-autostartup.html">Configuring
route startup ordering and autostartup</a>.</p><h3
id="Camel2.1.0Release-@Bean">@Bean</h3><p>@Bean now uses a <code>ref</code>
attribute to refer to the bean name. Also added a new <code>method</code>
attribute to set the method to use (optional).<br clear="none"> You need to
upgrade your code to use these attributes as the default <code>v
alue</code> have been removed. We assume only a very few people knew and uses
this @Bean annotation.</p><h3 id="Camel2.1.0Release-component"><a shape="rect"
href="direct.html">Direct</a> component</h3><p>The option
<code>allowMultipleConsumers</code> has been removed as it did not make sense
to have concurrent consumers on a direct endpoint.</p><h2
id="Camel2.1.0Release-KnownIssues">Known Issues</h2><p><a shape="rect"
href="routing-slip.html">Routing Slip</a> EIP does not break when Exchange is
failed, see <a shape="rect" class="unresolved"
href="#">CAMEL-2245</a>.</p><p>Using <transacted/> in Spring XML does not
work properly when using route scoped <onException> and/or
<onCompletion>. Using context scoped works. And the Java DSL does not
have this flaw. See <a shape="rect" class="unresolved"
href="#">CAMEL-2336</a>.</p><p>When using the <a shape="rect"
href="recipient-list.html">Recipient List</a> together with <a shape="rect"
href="mina.html">MINA</a> endpoints
Camel will over time hold on to memory which could lead to OutOfMemoryErrors.
See more at: <a shape="rect" class="external-link"
href="https://issues.apache.org/activemq/browse/CAMEL-2484";>CAMEL-2484</a></p><p>See
known issues from previous releases.</p><h2
id="Camel2.1.0Release-Importantchangestoconsiderwhenupgrading">Important
changes to consider when upgrading</h2><h2
id="Camel2.1.0Release-GettingtheDistributions">Getting the
Distributions</h2><h3 id="Camel2.1.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="extern
al-link"
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.1.0/apache-camel-2.1.0.zip";>apache-camel-2.1.0.zip</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="http://archive.apache.org/dist/camel/apache-camel/2.1.0/apache-camel-2.1.0.zip.asc";>apache-camel-2.1.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://archive.apache.org/dist/camel/apache-camel/2.1.0/apache-camel-2.1.0.tar.gz";>apache-camel-2.1.0.tar.gz</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="http://archive.apache.org/dist/camel/apache-camel/2.1.0/apache-camel-2.1.0.tar.gz.asc";>apache-camel-2.1.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">
-
-<p>The above URLs use the Apache Mirror system to redirect you to a suitable
mirror for your download. Some users have experienced issues with some versions
of browsers (e.g. some Safari browsers). If the download doesn't seem to work
for you from the above URL then try using <a shape="rect" class="external-link"
href="http://www.mozilla.com/en-US/firefox/"; rel="nofollow">Mozilla
Firefox</a></p>
+ <p>The above URLs use the Apache Mirror system to
redirect you to a suitable mirror for your download. Some users have
experienced issues with some versions of browsers (e.g. some Safari browsers).
If the download doesn't seem to work for you from the above URL then try using
<a shape="rect" class="external-link"
href="http://www.mozilla.com/en-US/firefox/"; rel="nofollow">Mozilla
Firefox</a></p>
</div>
</div>
-
-
-<h3 id="Camel2.1.0Release-SourceDistributions">Source 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> Source
for Windows </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.1.0/apache-camel-2.1.0-src.zip";>apache-camel-2.1.0-src.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.1.0/apache-camel-2.1.0-src.zip.asc";>apache-camel-2.1.0-src.zip.asc</a>
</p></td></tr></tbody></table></div>
-
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> Source for Unix/Linux/Cygwin
</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.1.0/apache-camel-2.1.0-src.tar.gz";>apache-camel-2.1.0-src.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.1.0/apache-camel-2.1.0-src.tar.gz.asc";>apache-camel-2.1.0-src.tar.gz.asc</a>
</p></td></tr></tbody></table></div>
-
-
-<h3 id="Camel2.1.0Release-GettingtheBinariesusingMaven2">Getting the Binaries
using Maven 2</h3>
-
-<p>To use this release in your maven project, the proper dependency
configuration that you should use in your <a shape="rect" class="external-link"
href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html";>Maven
POM</a> is:</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[
-<dependency>
+<h3 id="Camel2.1.0Release-SourceDistributions">Source 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>Source for Windows</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://archive.apache.org/dist/camel/apache-camel/2.1.0/apache-camel-2.1.0-src.zip";>apache-camel-2.1.0-src.zip</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="http://archive.apache.org/dist/camel/apache-camel/2.1.0/apache-camel-2.1.0-src.zip.asc";>apache-camel-2.1.0-src.zip.asc</a></p></td></tr></tbody></table></div><div
class="table-wrap"><table class="confluenceTable"><tbody
><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for
>Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><a shape="rect" class="external-link"
>href="http://archive.apache.org/dist/camel/apache-camel/2.1.0/apache-camel-2.1.0-src.tar.gz";>apache-camel-2.1.0-src.tar.gz</a></p></td><td
> colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
>class="external-link"
>href="http://archive.apache.org/dist/camel/apache-camel/2.1.0/apache-camel-2.1.0-src.tar.gz.asc";>apache-camel-2.1.0-src.tar.gz.asc</a></p></td></tr></tbody></table></div><h3
> id="Camel2.1.0Release-GettingtheBinariesusingMaven2">Getting the Binaries
>using Maven 2</h3><p>To use this release in your maven project, the proper
>dependency configuration that you should use in your <a shape="rect"
>class="external-link"
>href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html";>Maven
> POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div
>class="codeCo
ntent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-core</artifactId>
<version>2.1.0</version>
</dependency>
]]></script>
-</div></div>
-
-<h3 id="Camel2.1.0Release-SVNTagCheckout">SVN Tag Checkout</h3>
-
-<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[
-svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.1.0
+</div></div><h3 id="Camel2.1.0Release-SVNTagCheckout">SVN Tag
Checkout</h3><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[svn co
http://svn.apache.org/repos/asf/camel/tags/camel-2.1.0
]]></script>
-</div></div>
-
-<h2 id="Camel2.1.0Release-Changelog">Changelog</h2>
-
-<p>For a more detailed view of new features and bug fixes, see:</p>
-<ul><li><a shape="rect" class="external-link"
href="http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&styleName=Html&version=12315685";>JIRA
Release notes for 2.1.0</a></li></ul></div>
+</div></div><h2 id="Camel2.1.0Release-Changelog">Changelog</h2><p>For a more
detailed view of new features and bug fixes, see:</p><ul><li><a shape="rect"
class="external-link"
href="http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&styleName=Html&version=12315685";>JIRA
Release notes for 2.1.0</a></li></ul></div>
</td>
<td valign="top">
<div class="navigation">
![http://camel.apache.org/download.data/camel-box-v1.0-150x200.png"](http://camel.apache.org/download.data/camel-box-v1.0-150x200.png"){kind=link}
