Camel 2.1.0 release (Work in Progress)
New and Noteworthy
Welcome to the 2.1.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
- Pluggable API for Management allowing 3rd party to manage Camel.
- Use org.apache.camel.spi.ManagementStrategy to plugin 3rd party adapter
- Fine grained events notifications is now being emitted using org.apache.camel.spi.EventNotifier
- Events being fired can be created using a pluggable factory using org.apache.camel.spi.EventFactory
- Camel now supports using multiple org.apache.camel.spi.LifecycleStrategy strategies, that also allows 3rd party to more easily integrate into Camel.
- Overhaul of default JMX management in Camel to be much improved with more attributes, mbeans, operations, statistics, and route timing working as well.
- And yes you can now start/stop routes and individual consumers and producers
- And some special processors such as Delayer and Throttler can be managed to change their delay/throttle values
- You can dynamic manage tracing even for already running applications
- Error handling in Camel is now also manageable so you for example can change the redelivery policies.
- JMS consumers being restarted will pickup any configuration changes on JMS endpoints such as changing concurrentConsumers. And yes its fully managed using JMX.
- And much more...
- Improved IRC, XMPP, MINA, Freemarker and Velocity components with much thanks to the Camel community
- Splitter and Multicast EIP patterns now support the option stopOnException to stop continue processing at first exception occurred. See their documentation for more details.
- Error handlers is restricted to be configured on camel context and/or routes only.
- Camel is now more robust and fault tolerant when shutting down.
- Fixed a race condition when shutting down Camel with JMS consumers that under some circumstances caused it to appear to hang
- Added pluggable org.apache.camel.spi.InflightRepository with a basic implementation that can help with graceful shutdown as you can now see how many exchanges are currently in progress.
- JmsEndpoint is now singleton
- Individual routes can be pre configured to not auto startup when Camel starts: autoStartup=false in XML DSL and noAutoStartup() in Java DSL.
- 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.
- Improved unit test coverage, now having 3500+ unit tests in total.
- Fixed ConsumerTemplate not working when it was dependency injected with @EndpointInjected in a Bean.
In the Java DSL the .errorHandler 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 .from DSL.
In Spring DSL the errorHandlerRef attribute is now only visible on the <camelContext> and <route> XML tags.
New .jar dependencies
camel-core now depends on commons-management.jar to facilitate the new overhauled management.
This project is hosted at FuseForge
This .jar can be retrieved from the maven central repo at: http://repo1.maven.org/maven2/org/fusesource/commonman/commons-management/1.0/
The maven dependency details are:
CamelContext have renamed the method getLifecycleStrategy to getLifecycleStrategies and now returns a List.
The API in org.apache.camel.spi.ManagementNamingStrategy had its methods renaming and method signature adjusted to accommodate the big theme for Camel which was overhaul of management (JMX).
- org.apache.camel.processor.CompositeProcessor was never used
- org.apache.camel.impl.ProducerTemplateProcessor was never used
- org.apache.camel.impl.NoPolicy was never used
- org.apache.camel.spring.handler.LazyLoadingBeanDefinitionParser was never used
- org.apache.camel.spring.handler.ScriptDefinitionParser was never used
See known issues from previous releases.
Important changes to consider when upgrading
Getting the Distributions
|The above URLs use redirection|
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
Getting the Binaries using Maven 2
To use this release in your maven project, the proper dependency configuration that you should use in your Maven POM is:
SVN Tag Checkout
For a more detailed view of new features and bug fixes, see the:
TODO: Fix for 2.1.0