Welcome to the 2.4.0 release which approx 182 issues resolved (new features, improvements and bug fixes such as...)
asyncDelayedRedelivery
.<contextScan>
to scan the Registry for RouteBuilder
instances, just as scanning the classpath etc.MultiPartForm
with Jetty.Numeric
positionsuseOriginalBody
to OnCompletion@Consume
not running in an unit of work to ensure callbacks is invoked when its doneManagementAgent
settings can now be set using setters from Java, instead of having to use JVM system properties. See tip in Camel JMX wiki page.allowDuplicates
and reverse
which allows you to use it for re-ordering messages from JMS queues based on JMSPriority
ProducerTemplate
API a bit, see more details in the section Important changes to consider when upgrading.quartz.properties
file to load from classpath.StartupListener
to allow components/endpoints/producers/consumers etc. as a listener to be notified when CamelContext
have just been started. This allows any custom logic to be executed as a late starter. This ensures Quartz scheduler is only started when all the routes and so forth is started and running."ftp:admin:secret@someserver//absolutepath/foo/bar"
.fromRoute
to NotifyBuilder.CamelContext
internal LRUCache.simple
and xpath
expression builder methods out of the box.tokenizer
not being able to delete/move file after processing is done on Windows platform.maxMessagesPerPoll
is now applied eagerly to limit intaking files earlier for the File and FTP components, Thus avoid excessive memory consumption if you poll directories which contains 100.000+ files.connectTimeout
, soTimeout
and timeout
to FTP so its easier to configure timeouts.beanRef
and methodCall
DSLs will eager check on startup, the bean reference exists in Registry and the provided method name is a valid method name on the bean as well. This helps to fail fast if end users have a typo in their routes.ExchangeRedeliveryEvent
event being emitted when Camel Error Handler attempts a redelivery.java.util.Properties
from the Registry using the ref:
prefix.@RoutingSlip
The ToAsync has been removed and replaced with a better asynchronous routing engine.
Routing Slip now requires using Expression to specify the routing slip header, the XML DSL of Routing Slip is broken.
<route> <from uri="direct:a"/> <!--NOTE from Camel 2.4.0, you need to specify the expression element inside of the routingSlip element --> <routingSlip ignoreInvalidEndpoints="true"> <header>myHeader</header> </routingSlip> </route> |
The retryUntil
method on onException have been renamed to retryWhile
to better match what it does. It keeps retrying while the predicate returns true
.
org.apache.camel.spi.Policy
now has an additional method beforeWrap
which means you need to implement this method in your implementations. Just add a empty method to adapt.
The class org.apache.camel.management.event.ExchangeFailureEvent
has been renamed to org.apache.camel.management.event.ExchangeFailedEvent
.
The Tracer may not output all details for some situations such as when using onCompletion
or intercept
etc.
Not all Examples have ANT build.xml files to run the example using ANT.
The read timeout
in Netty is causing it to spawn threads and you end up with out of memory error. You have to disable using timeout by setting the timeout=0
in the endpoint configuration. This issue has been fixed in the next release.
The LoggingErrorHandler does not work when also using onException. It may go into an endless loop. So refrain from using logging error handler.
The JMX statistics for type=processors
is being counted double. The stats on the type=routes
is correct though.
The Jetty component sends back HTTP headers with lower-case keys.
HawtDB does not work in OSGi
HawtDB has a bug in version 1.4 or older which prevents the filestore to free unused space. Version 1.5 fixes this.
There is a concurrency issue when using predicates using binary operators such as isEqualTo
. See CAMEL-3188.
The FTP consumer may stop continue polling. You can start the consumer from eg. a management console and it will start again.
Camel now uses Spring 3.0.3 as the default Spring version. Spring 2.5 is still supported.
Spring 2.0.x support is now @deprecated and will in future releases not be supported.
Mind that Spring 3.0 has changed how it performs dependency injection. In fact it may even perform this differently than what Spring 2.5 would do. For example the order and which beans is dependency injected on startup could potential affect your existing Camel applications when upgrading. It appears as Spring 3.0 has gotten worse in this area and you may have to specify |
IntrospectionSupport
has been improved to be consistent for getProperty
and getProperties
. Also getProperties
now find all relevant properties. This will often only be relevant for Camel end users who build their own components any may use IntrospectionSupport
.
The ProducerTemplate
have been tighten up a bit. All send/request -body
methods will now throw a CamelExecutionException
with the cause wrapped. This ensures its consistent.
The ftps
is now using secure data channel also when transferring files. There has been added some options which you can use to control the behavior and turn it off if you want the old behavior (only secure login).
The FTP starting directory can now be set using absolute paths as well. In the endpoint uri just define two leading / to indicate absolute, eg "ftp:admin:secret@someserver//absolutepath/foo/bar"
.
The default port from ftps
has been changed from 2222 to 21.
The FTP is now using a default of 10 sec connect timeout (ALL), and 30 sec data timeout (FTP/FTPS only).
The RouteBuilder now have simple
and xpath
expression builder methods out of the box, which means you don't have to use static imports to use those two Languages. The compiler may complain if you have a static import, which you simply fix by removing the static import.
Description | Download Link | PGP Signature file of download |
---|---|---|
Windows Distribution | ||
Unix/Linux/Cygwin Distribution |
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 FireFox |
Description | Download Link | PGP Signature file of download |
---|---|---|
Source for Windows |
Source for Unix/Linux/Cygwin |
To use this release in your maven project, the proper dependency configuration that you should use in your Maven POM is:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-core</artifactId> <version>2.4.0</version> </dependency> |
svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.4.0 |
For a more detailed view of new features and bug fixes, see: