This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Camel 2.11.0 Release
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Camel 2.11.0 release (currently in progress)

Unknown macro: {div}

Unknown macro: {div}

New and Noteworthy

Welcome to the 2.11.0 release with approximately XXX issues resolved - including new features, improvements, and bug fixes, such as:

  • Added support for SOAP 1.2 in SOAP data format.
  • Cache operation for add/update now supports expiry headers to control time to live/idle/eternal.
  • Added allowNullBody option to JMS to configure whether sending messages with no body is allowed.
  • Added connectOnStartup option to HDFS to allow to connect on demand, to avoid having Hadoop block for long time connecting to the HDFS cluster, as it has a hardcoded 15 minute retry mechanism.
  • Added support for daily and weekly trends to Twitter component.

Fixed issues

  • Fixed RoutePolicy used from Spring XML with routePolicyRef may not invoke all callbacks on the policy.
  • Fixed MINA consumer to force disconnect upon timeout when doing request/reply, as late replies may cause side effects otherwise.
  • Fixed Simple language with empty quoted literals in predicates, so you can compare against empty strings.
  • Fixed SOAP data format to set SOAP 1.1 namespace when marhsalling faults.
  • Fixed SEDA producer to send to the right BlockingQueue being attached on the SEDA endpoint so that the sent messages don't get lost.

New Enterprise Integration Patterns

New Camel Karaf Command

New Components

DSL Changes

New Annotations

New Data Formats

New Languages

New Examples

New Tutorials

API changes/breaking

  • Changes goes here!!!

Internal/Non API refactorings that may affect users

  • Changes goes here!!!

Known Issues

  • The Tracer may not output all details for some situations, such as when using onCompletion or intercept, etc.
  • The project cannot fully build the site using Maven (e.g. running "mvn site"). There is no plan to fix this, as the project does not use maven site.
  • JBoss 7 may log a WARNing when running Camel as a WAR file.

Dependency Upgrades

  • Axiom 1.2.10 to 1.2.13
  • BeanIO 2.0.0 to 2.0.1
  • Castor bundle 1.3.1_2 to 1.3.2_1
  • Ehcache bundle 2.5.1_1 to 2.5.2_1
  • Netty 3.5.1 to 3.5.2
  • Ognl bundle 3.0.4_1 to 3.0.5_1
  • Spring Framework 3.1.1 to 3.1.2
  • Spring Integration 2.1.2 to 2.1.3
  • Woodstox 4.1.2 to 4.1.3

Important changes to consider when upgrading

  • Important stuff goes here!!!


  • Maven 3.0.2 or better is required to build the Source
  • If you want to deploy Apache Camel 2.11.0 into Apache Karaf, we highly recommend to use the '' configuration, which is part of Apache Karaf 2.2.5 onwards. For example camel-cxf, camel-mail, and camel-spring-ws requires this to be installable; as well other features may as well.

Getting the Distributions

Binary Distributions


Download Link

PGP Signature file of download

Windows Distribution

Unix/Linux/Cygwin Distribution



Source Distributions


Download Link

PGP Signature file of download

Source Distribution

  • No labels