The Apache Camel PMC welcomes Martin Krasser as a new committer.

Martin has been a Camel rider for more than 2 years. In this time he pointed out bugs, submitted patches, contributed to discussions and helped out other users on the mailing lists. We appreciate his outstanding contributions and we look forward to his continued involvement in the future.

Please buy Martin a beer next time you see him .

Hadrian (on behalf of the Camel PMC)

The Camel riders are pleased to introduce the Apache Camel 2.0.0 Release. This is a major overhaul of Camel that took more than a year of efforts and is coming with about 760 issues resolved. We are grateful to the entire community for its involvement. Your hard work and constant attention to details promoted Apache Camel to wider adoption and leadership position in the integration space.

The feature and improvements list is too large to fit here, so please check out the release notes. Note that along with many improvements came a few api changes and migration from the 1.x line, while not too complicated, is not straightforward. The old Camel 1.x branch will still be supported for a while although the upgrade to this hot release is strongly encouraged.

Many thanks to all the contributors who made this release possible. Download Camel now and enjoy the ride!
The Camel Riders

Welcome to the Camel 2.0-M3 Release which approx 109 issues resolved (new features, improvements and bug fixes such as...)

• Complete removal of specialized Exchange using generics
• Performance improvements
• JMS improvements and fixes
• Fixes for Camel Maven Archetypes.
• Spring DSL fixes.
• Added SSL support to Camel IRC
• Many fixes in the CXF, FTP, Log, Mail and other.
• Major improvements and fixes in Bindy
• Removed platforms specific encoding from kits.
• Fixed issues related to class loading in OSGi.
• Upgraded to Junit 4.5.

Many thanks to all contributors for the great effort.

The Camel Riders

We are pleased to introduce the Apache Camel 2.0-M2 release with approx 222 issues resolved. This will probably be the last milestone release and the the final 2.0 will follow soon. The api changed from the 1.x version, but is now stable and we don't anticipate any changes in the upcoming 2.0. If you didn't already start migrating to the 2.0 line, now it's probably a good time to do so.

Among the new features, improvements and bug fixes in this release (from the 1.x version):

• Introduced type converter registry to allow end users to programmatic get access to this registry
• major improvements and refactoring of most components (see release notes)
• RedeliveryPolicy added support for ref attribute to reference a existing policy in the Registry
• 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.
• Multiple inputs can be define as input to routes: from("activemq:queue:order", "file://order").to("bean:handleOrder");
• 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.
• 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
• Introduced ConsumerTemplate supporting the Polling Consumer EIP
• Custom endpoints with Spring @ManagedResource is now also registered in the mbean server.
• The default error handler is changed from Dead Letter Channel to DefaultErrorHandler.
• Overhaul and improvements to the Try Catch Finally DSLs, so they are on pair with the Exception Clause.
• Overhaul and improvements to the Intercept DSLs. Added new interceptSendToEndpoint to intercept sending to a given Endpoint.
• Added the notion of a Channel in the routes.
• Added support to navigate the routes at runtime, so you can dynamic change or affect the processors in the routes.
• Introduced a new Async API for asynchronous messaging.
• Added Failover as load balancer.
• Added Jackson as supported library for the JSON data format.

Many thanks to everybody who contributed to this major effort.
The Camel riders.

Camel 1.6.1 release

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

• Performance enhancement when sending high load of messages through Camel
• Fixes for thread safety for LDAP, Validation, JAXB data format.
• Use Nexus for releases.
• Fixed issue with start/stop state machine.
• Upgraded to CXF 2.2.
• Security improvements for Jetty.
• HL7 fixes on Windows platforms.
• Fixes for header propagation in Bean component.
• Fixes for using injected Endpoint.
• Message Exchange Pattern can now be changed directly in the DSL.

Many thanks to the Camel community for its active involvement.
The Camel Riders

Welcome to the the Camel 2.0-M1 release, the first milestone release of the new Apache Camel 2.0 project. We know many of you were expecting it. While it is just the first milestone release and a few changes are still in the pipeline, most of the API changes are in, so that you won't have to migrate twice. The core and most of the components you used for quite a while now are stable.

So what's new? Quite a lot. With about 368 issues resolved (new features, improvements and bug fixes) it is the largest change set in Camel's history. The apache-camel-2.0-M1 version comes with:

• New Examples
• New Enterprise Integration Patterns: Sort
• New Components: Cometd, Freemarker, Restlet, RSS, Web Console (experimental)
• New Data Formats: Bindy, JSON, TidyMarkup, Zip, XMLSecurity
• New Languages: Mvel, Property
• New annotations: @FallbackConverter
• 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.
• Improved tooling being able to retrieve more runtime information from the CamelContext
• And much, much more...

Enjoy,
The Camel Riders

We are pleased to announce the new Camel 1.6.0 Release which includes the following new and noteworthy features! Get it while its hot!

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

• RedeliveryPolicy added support for ref attribute to reference a existing policy in the Registry
• major improvements to Jetty for better handling of exception and faults and easier end-user customization how response should be written
• minor improvements to HTTP and MINA
• HTTP supports authentication
• MINA producer now throws CamelExchangeException in case no response received from remote server when in sync mode (sync=true)
• SFTP added support for knownhosts, privatekey files and passive mode
• Added onWhen predicate to Exception Clause
• Exception Clause is much smarter as it will use caused by exception hierarchy for matching as well (will use bottom ups)
• Dead Letter Channel now have onRedeliver to allow custom processing an Exchange before its being redelivered. Allowing you to work on the message being sent.
• Message Exchange Pattern can now be changed directly in the DSL.

Apache Camel has successfully completed the infrastructure transition after becoming a TLP. There are still a few wrinkles to iron out on the trunk. During the next few weeks the main focus will be a Camel 1.6 release. We know many of you are waiting for it.

Many thanks again to our growing community. All this is only possible because of your support and contributions.

The Camel Riders

As per the board resolution of Dec 17th, 2008, Apache Camel is a top level project. The new url is http://camel.apache.org. Contributions are always welcome and highly appreciated!

This would not have been possible without the valiant efforts made by the growing community, contributors and committers. Many thanks everybody!

The Camel riders.

Camel 1.5.0 release

New and Noteworthy

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

• support for Guice for dependency injection along with a new Guice JMS Example
• major improvements in FTP and File components
• File consumers now default uses exclusive read locking when it consume files, meaning that they wont consume files that are in the progress of being written by third part. The FTP consumer has this support as well, however it is disabled by default as it requires write privileges.
• File and FTP component supports expression to set dynamic filename patterns instead of using the FileComponent.HEADER_FILE_NAME header. See File Language for samples and use cases.
• important changes in ProducerTemplate (see below)
• Exception Clause now supports marking exceptions as being handled so callers doesn't receive the caused exception, but you can set the response to return instead. This is a very important feature.
• various improvements in Flatpack and XMPP components
• minor improvements in CXF, SpringIntegration, HTTP, Mail and MINA components
• minor improvements in Aggregator supporting a better fluent builder, etc.
• Splitter now handles streaming avoiding reading entire content into memory (consuming very big 1gb files is now possible)
• introduced new JT400, HL7, LDAP and Smooks components
• introduced Delay Interceptor to slow down processing to show how things is happening nice and slow, so you are not bombarded with zillions of logging output.
• Mail can now send html mails with the new contentType option
• Camel Maven Archetypes now available in m2eclipse Maven project creation
• Java WebStart support
• refinements in loading resources using OSGi bundles, should now handle different OSGi platforms much better
• Type Converter now supports Exchange as 2nd parameter to allow converters access to the Exchange and thus the CamelContext as well. To be used for setting encoding in the future.
• New Loop api in DSL allows processing of a message a number of times, possibly in different ways.
• Spring DSL improve
• improved Tracer formatting and more options for configuration
• improved support for all Endpoints, not just singletons in CamelContext.
• minor tweaks to the Visualisation generator
• IBM JDK support (notable exceptions)

New and Noteworthy

Welcome to the new Camel 1.4.0 Release which includes 261 new features, improvements and bug fixes such as...

• major improvements in JMS and Mail components
• major improvements in Camel JMX management (enabled by default)
• major improvements in Transactional Client. Bypassing Dead Letter Channel redelivery, letting the originator system handle this, resulting in the JMSMessage is rolled back to the JMS queue.
• attachment support for Message
• various improvements in CXF, File, FTP, Velocity, Stream, Atom and XMPP components
• various improvements in the Java and Spring DSL
• new transaction error handler, see Transactional Client
• introduced ExceptionPolicyStrategy as strategy for exception clause selection during error handling (much improved default strategy in Camel)
• intercept() default behavior changed (see section - important changes)
• JMS headers now preserve packagename style headers so Bean and File headers is preserved, so you can safely send the filename or bean method to invoke over the JMS wire
• introduced Debugger and Tracer interceptor to track how exchanges is routed
• refinements to run in OSGi containers
• some internal refactorings of package structure to avoid cycle dependencies
• @deprecated some core classes, that will be removed in Camel 2.0
• improved feedback for misconfiguration of camel routes such as mistypes of parameters
• overall improved wiki documentation
• improved javadoc for camel-core and camel-spring
• dependencies is now on the finer grained jars if applicable (e.g. Spring)
• WebSphere 6.1 support

New Enterprise Integration Patterns

• None

New Components

• Flatpack for processing fixed width or delimited files or messages using the FlatPack library (work in progress)
• SpringIntegration for integration with Spring Integration

New DSL

• Scala (work in progress, not fully feature complete)

New Data Formats

• None

New Languages

• None

New Examples

• ANT build files for running the examples
• camel-example-loan-broker
• camel-example-spring-jms

Please see Release Notes for more details. Download it now while is hot!
The Camel riders

JavaOne Meetup 2008

Come meet with the folks behind Apache ActiveMQ, Camel, CXF and ServiceMix at JavaOne!

In an attempt to help predict the head count, please add your name to the registration page.

A couple weeks ago I spoke at ApacheCon EU 2008 in Amsterdam, The Netherlands about Apache Camel. If you weren't able to attend, don't worry as the presentation, named Take Apache Camel for a Ride can be downloaded now. If you have any questions, please contact me as my presentations don't contain many bullet points because I tend to elaborate verbally on the topic.

We are very pleased to announce the new Camel 1.3.0 Release which includes 208 new features, improvements and bug fixes such as...

• improved Bean Integration
• improved testing via Spring Testing along with the Mock, Test, DataSet components
• browsing of endpoints via the BrowsableEndpoint with support in the JMS, List, Mock, SEDA and VM components
• improved support for message exchange patterns such as InOut for JMS
• various improvements in CXF, iBATIS, Jetty, MINA components
• improved XPath and XQuery support in Spring XML and with easier namespace configuration
• default to more efficient JMS usage when working with Spring 2.5.x to avoid a previous Spring bug
• various improvements in the DSL and with error handling
• improved automatic Type Converter implementations
• method invocations now supported in EL expressions
• CXF transport API now supported in CXF component, you could leverage the power of Camel mediation in Apache CXF

New Components

• AMQP
• DataSet for easier load testing
• JCR for JSR 170 support
• List for UI and tooling integration
• Stream for working with input/output streams
• Test for easier functional testing
• XQuery for easy XQuery based transforms for Templating

New Data Formats

• CSV
• XmlBeans
• XStream

New Languages

• Bean Language
• JXPath

New Enterprise Integration Patterns

• Load Balancer
• Routing Slip

Please see Release Notes for more details. Download it now while is hot to trot!

Enjoy,
The Camel riders

I'm pleased to announce the Apache Camel 1.2.0 Release has been made! Its packed with a ton of new feature such as:

• Data Format to support pluggable marshalling and unmarshalling of data in various formats like JAXB, XML Beans, Serialization or Artix Data Services
• hugely improved CXF integration for working with JAX-WS and Apache CXF while reusing powerful Camel routing.
• improved support for Asynchronous Processing within components such as for HTTP and SEDA
• improved OSGi support with both component discovery using the OSGi registry and turning Camel into OSGi bundles.
• improved Visualisation
• support for the full WSDL Message Exchange Patterns
• more powerful Bean Integration

Go take it for a ride!

There is a new short ScreenCast from James Strachan which gives a brief introduction to Apache Camel and the Enterprise Integration Patterns. Check them out!

• Introduction to Camel and Enterprise Integration Patterns (Medium Resolution)
• Introduction to Camel and Enterprise Integration Patterns (High Resolution)

We now have a nice EIP Visualisation maven plugin available! So you can now easily generate nice graphical reports of your EIP routing rules from your application code.

We've also added the generation of these EIP diagrams to the standard maven reports via the Camel Maven Plugin. For example here's the generated example routing rules for the camel-spring module. Notice how you can click on most of the EIP nodes to go to the pattern page! And hover over a node to get more detailed description etc.

For a description of theplugin and how it works is see here.In summary; just add the camel-maven-plugin to your <reporting> section of your pom.xml then make sure you have a META-INF/spring/*.xml in your classpath which configures your EIP routing rules (via Java or XML). Note that if you do not intend to include a META-INF/spring/*.xml file in your jar, you could put this in the src/test/resources directory so it will only be used for generating the reports.

James Strachan was interviewed by Dana Gardner on Apache Camel and its DSL and support for Enterprise Integration Patterns. Read the transcript or check out the podcast.

I'm pleased to announce the Apache Camel 1.1.0 Release has just been made! Its packed with a ton of new feature such as