Welcome to the 2.5.0 release which approx 300 issues resolved (new features, improvements and bug fixes such as...)
suspend/resume
operations to CamelContext for warm restarts, or as the preferred way to temporary stop a running Camel application, and then later resume it. Those operations is also available in JMX.removeRoute
to remove a route from JMX. Routes with autoStartup=false
is now also listed in JMX, to allow you to start the routes manually.synchronous=true
in the endpoint uri.cd <dir>, list files in cur dir
pattern, as opposed to a list files <dir>
style.httpClient
parameters.InOut
message to Dead Letter Channel would cause Camel to expect a reply. Now the message will always be send to the DLQ as InOnly
.disableReplyTo
was not used.IllegalStateException
CamelContext
after it had been shutdown, leading to routes not properly being re-initialized and started.preMove
together with either noop
or delete
options.timeout
in Recipient List, Splitter and Multicast EIPs when running in parallel mode.JavaUuidGenerator
, especially in high concurrent systems.and
or or
operator. Now you can use multiple operators in the same expression.dynamicRouter
to the DSL to make it easier to do dynamic routing using a Bean to evaluate on-the-fly the next destination(s).JMSReplyTo
header configured, then the JmsProducer
will lookup/create the JMS Destination to ensure its a valid JMSReplyTo
from the header.language
endpoint. This makes it easier to support Dynamic Router where small pieces of logic must be executed as well.charset
option on the File, FTP endpoint which dictates the encoding to use.synchronous
option to true
.providers
option on the CXFRS endpoint.ConsumerTemplate
using receiveBody
methods to complete OnCompletion beforehand. For example when using a File endpoint and having set delete=true
, which now causes the file to be deleted.<bean>
and <camelContext>
, making it work as it did with Spring 2.5 when using Spring 3.0 instead. The <bean>
will be dependency injected before the <camelContext>
.String
types which will fallback and lookup PropertyEditor
editors.LimitedPollingConsumerPollStrategy
for Polling Consumers as a limited strategy which suspends consumers which causes consecutive failures. For example to avoid a faulty consumer to spam logs etc. Uses a limit of 3.PropertyPlaceholderConfigurer
. See example at the File language page.discardOnCompletionTimeout
option to AggregatorisEqualTo
."Ibsen, Claus" <davsclaus@apache.org>
style.publishedEndpointUrl
option into the CXF component.DefaultPackageScanClassResolver
supports to configure the url schemes by using Spring configuration. To cater for Server's using custom classloader schemes in URLs.lazyLoadTypeConverters
to CamelContext to configure if type converters should be loaded lazy or on startup (default).@DynamicRouter
camel-example-reportincident-ws-security-osgi
protected
to public
to make it easy from Java code to re-use the functionally of those methods, without using it as a Camel component. Such as when you want to communicate with a FTP server using the API from the RemoteFileOperations
.changeToParentDirectory
method to GenericFileOperations
.onCompletion
or intercept
etc.camel-blueprint
is not fully feature complete (such as @Producer, @Consume is not supported)camel-blueprint
using <package> scan does not workcamel-jms
is compiled against Spring 3.0. See more at CAMEL-3286markRollbackOnlyLast
doesn't remove caused exception, which may affect outer transaction to rollback as well. Likewise the logging of TransactionErrorHandler
may log the inner transaction as being committed, when it was in fact rolled back.parallelProcessing
may use a lot of memory during processing, see CAMEL-3497stopRoute
method on CamelContext
now leverages Graceful Shutdown when stopping. This is more intuitive to stop routes in a graceful and safe manner. You can the stop method with a timeout if you want to force stopping, which was the old behavior.camel-core-tests.jar
and camel-spring-tests.jar
has been deprecated and will be removed in a future release. You should always only use the camel-test.jar
if you want to use the Camel Test Kit.<camelContext>
it would have defaulted to camelContext
. This has been changed to be the auto assigned name it's given by Camel, such as camel-1
, camel-2
etc.timeout
option on Netty has been removed as it was flawed.clientId
, otherwise Camel will fail fast on startup.JavaUuidGenerator
as the ActiveMQ may use JDK API which is not accessible in the cloud.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.5.0</version> </dependency> |
svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.5.0 |
For a more detailed view of new features and bug fixes, see: