Camel 2.7.0 release (currently in progress)

New and Noteworthy

Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)

• Switched to use slf4j as the logger instead of commons logging.
• Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
• Added support for MDC logging with Camel
• JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
• Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
• Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
• Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
• HTTP4 is upgraded to use Apache HttpClient 4.1
• Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
• Fixed concurrent append to the same file in the File producer
• Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
• Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
• Quartz update checker is now always disabled, see more details here
• Fixed potential issue installing camel-ftp feature in Apache ServiceMix
• New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
• Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
• Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
• Introduced <redeliveryPolicyProfile> to easily define common profiles for redelivery policies, which you can refer to from <errorHandler> or <onException> using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with <redeliveryPolicyProfile>.
• Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
• Spring Integration is upgraded to Spring Integration 2.0.
• Spring Web Services is upgraded to Spring Web Services 2.0.
• Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
• Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage.

New Enterprise Integration Patterns

• None

New Components

• Context
• MyBatis

New DSL

• <setFaultBody> added to XML DSL
• endChoice added to Java DSL
• placeholder added to Java DSL

New Annotations

• None

New Data Formats

• None

New Languages

• Spring Expression Language

New Examples

• camel-example-osgi-rmi

New Tutorials

• None

API breaking

• FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead.
• org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses slf4j as the logger.
• Removed getLeftValue and getRightValue methods on BinaryPredicate.
• The ref attribute on <redeliveryPolicy> has been removed. Instead use redeliveryPolicyRef attribute on <onException> or <errorHandler> tags.
• The <batch-config> and <stream-config> tags in XML DSL in the Resequencer EIP must now be configured in the top, and not in the bottom. So if you use those, then move them up just below the <resequence> EIP starts in the XML.
• The JdbcAggregationRepository is moved from the camel-jdbc-aggregator component to the camel-sql component. The full qualified class name changed from org.apache.camel.component.jdbc.aggregationRepository.JdbcAggregationRepository to org.apache.camel.processor.aggregate.jdbc.JdbcAggregationRepository.

Known Issues

• 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.
• Project cannot be fully build using Maven 3.0
• camel-script which uses ScriptEngineManager from the JDK, cannot load script engines from packages outside the JDK.
• Stopping a route after using adviceWith maybe cause issues with error handlers, see CAMEL-3534

Important changes to consider when upgrading

• Java 1.6 or better is required
• Spring 3.0.x or better is required, when using Spring
• Apache CXF 2.3.2 or better is required, when using CXF
• Switched to use slf4j as the logger instead of commons logging. That means you may have to included slf4j-log4j12 as dependency if you are using log4j.
  See documentation at slf4j for more details.
• If you have developed custom Camel Components and your Endpoint class extends DefaultEndpoint then its advised to use the doStart and doStop instead of start and stop.
• camel-cxf endpoint will copy the attachments between the camel message and cxf message when it works in POJO data format, please access the attachment objects from the camel message body.

Getting the Distributions

Binary Distributions

Source Distributions

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:

<dependency>
  <groupId>org.apache.camel</groupId>
  <artifactId>camel-core</artifactId>
  <version>2.7.0</version>
</dependency>

SVN Tag Checkout

svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.7.0

Changelog

For a more detailed view of new features and bug fixes, see the:

• release notes for 2.7.0