Camel 2.0.0 release (Work in progress)

New and Noteworthy

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

• Introduced type converter registry to allow end users to programmatic get access to this registry
• major improvements to Jetty for better handling of exception/faults and easier end-user customization how response should be written
• major improvements to [File] for consuming files, now supporting pluggable sorting, filtering and idempotent repositories.
• major refactor and improvements to FTP, aligning it with the [File] component.
• minor improvements to JDBC, SQL, HTTP and MINA
• major refactor and improvements to CXF component.  CxfBinding, HeaderFilterStrategy, Bus can be looked up from registry and configured at the endpoint level.
• [File] and FTP producers added option to write files using a temporary name and then rename it to the real name after the write completes
• SFTP added support for knownhosts and privatekey files
• Mail now supports setting additional SUN java mail properties
• MINA now supports setting text line delimiters for textline codec.
• MINA producer now throws CamelExchangeException in case no response received from remote server when in sync mode (sync=true)
• RedeliveryPolicy added support for ref attribute to reference a existing policy in the Registry
• RedeliveryPolicy added delayPattern option for using a special pattern for setting different delay based on intervals
• Added onWhen and retryUntil predicates to Exception Clause
• List component renamed to Browse
• Exception Clause is much smarter as it will use caused by exception hierarchy for matching as well (will use bottom ups)
• Dead Letter Channel and Exception Clause now have onRedeliver to allow custom processing an Exchange before its being redelivered. Allowing you to work on the message being sent.
• Added support for [\# syntax in Endpoint URI's] to allow endpoint URI's to refer to bean in the Registry.
• consumer. prefix can be omitted for scheduled polling consumers such as [File], FTP consumers. Thus the URI options is more simpler and you don't have to remember which requires consumer. prefix and which doesn't.
• Tracer improved to allow custom routing and processing of TraceEventMessage so you can store trace logs as you like, for instance in a database.
• Tracer now also displays the previous node so you can see where the Exchange is coming from.
• Quartz has added support for stateful jobs.
• Introduced @FallbackConverter for using annotation based fallback type converters
• Extended content enrichment support via the enrich DSL element.
• Simple language now supports a basic set of operators.
• Aggregator now supports grouped exchanges out of the box, so you can combine all aggregated exchanges into a single grouped exchange going out.
• Multiple inputs can be define as input to routes: from("activemq:queue:order", "file://order").to("bean:handleOrder");
• CXF component supports a new "cxfbean" endpoint that allows RESTful requests to be routed to JAXRS annotated service beans.
• Setting cron expression in camel-quartz improved.
• Better handling of interrupts while shutting down.
• The JMSReplyTo destination is available as Exchange property when consuming JMS messages.
• Better support for InOptionalOut Message Exchange Pattern.
• Pluggable Class Resolvers SPI for class resolvers allowing third party platforms such as JBoss to provide integration with Camel.
• Refined API to reduce package tangling.
• Introduced wireTap node for the Wire Tap EIP pattern, supporting the traditional tapping and sending a new message.
• Added fromF and toF in the Java DSL to build uri strings using String.format with arguments, e.g.: fromF("ftp://%s@myserver?password%s", user, password)..to
• Improved tooling being able to retrieve more runtime information from the CamelContext
• Scala DSL is improved
• Added JmsMessageType option to JMS to allow you to set which javax.jms.Message implementation to use for sending a JMS message.
• Fixed a rare bug when JMX is disabled, a Dead Letter Channel could mistakenly be added to some routes, when a global noErrorHandler was configured.
• JMS is now able to preserve hyphen in JMS keys (eg Content-Type can be sent as a Message header). Introduced pluggable strategy to allow end users to use their custom key formatter for encode/decode.
• Added option transferExchange to JMS so you can transfer the Exchange over the wire. Can be used to use JMS queues for Dead Letter Channel to preserve all information from the failed Exchange including the original exception with stack trace.
• Added option transferException to JMS so when using Request Reply messaging with JMS, any caused exception on the server side will be returned as response to the client.
• Added rollback as DSL keyword to force a rollback of the given Exchange. Does this by throwing an org.apache.camel.RollbackExchangeException.
• Added SOAP Message Header filtering capability in camel-cxf component.
• ProducerTeamplate API reworked for sendBody operations to return void, as they are InOnly. Use requestBody if you need InOut.
• Introduced ConsumerTemplate supporting the Polling Consumer EIP

New Enterprise Integration Patterns

• Sort

New Components

• Cometd
• FreeMarker
• Restlet
• RSS

New DSL

• Scala

New Annotations

• @FallbackConverter

New Data Formats

• Bindy
• JSON
• TidyMarkup
• GZip
• Zip
• XMLSecurity

New Languages

• Mvel
• Property

New Examples

• camel-example-pojo-messaging shows how to use annotations to produce, consume or route messages to Camel endpoints without using any DSL.
• camel-example-reportincident is based on a real life use case.
• camel-example-tracer is a new example showing Tracer persisting trace events into a database using JPA

API breaking

Client API

ProducerTemplate

The sendBody methods now return void for InOnly messaging. Use requestBody if you want InOut messaging.

Notable changes to DSL

• Renamed DSL operations
  • splitter -> split
  • resequencer -> resequence
  • aggregator -> aggregate
  • delayer -> delay
  • throttler -> throttle
  • expression -> language

Components

• The List component is renamed to Browse component
• The Queue component has been removed
• The FTP component have renamed some of its URI options
• The [File] component have renamed some of its URI options
• The CXF component have been refactored and APIs have been simplified

Known Issues

See known issues from previous releases.

Important changes to consider when upgrading

JAXB data format

If you use XJC to create the java class from the schema, you will get a ObjectFactory for you JAXB context. Since the ObjectFactory uses JAXBElement to hold the reference of the schema and element instance value, from Camel 1.6.0 jaxbDataformat will ignore the JAXBElement by default and you will get the element instance value instead of the JAXBElement object form the unmarshaled message body.
If you want to get the JAXBElement object form the unmarshalled message body, you need to set the JaxbDataFormat object's ignoreJAXBElement property to be false.

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.0.0</version>
</dependency>

SVN Tag Checkout

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

Changelog

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