Page History

...

• Spring 3.0.3 is now the default Spring version used by Camel.
• Fully non blocking Asynchronous Routing Engine which all EIPs and some Camel Components supported.
• New feature to use scheduled delayed redelivery attempts (they are fully asynchronous and non blocking). You need to enable this using the option asyncDelayedRedelivery.
• Fixed a potential dead-lock when using Aggregator with timeout completion set.
• The camel-spring module now supports OSGi out of box, which renders camel-osgi as @deprecated.
• OSGi blueprint is now supported
• Added new <contextScan> to scan the Registry for RouteBuilder instances, just as scanning the classpath etc.
• Manually started routes is now also Graceful shutdownShutdown by Camel
• Fixed issue using RouteContextRef with multiple CamelContext from the same Spring ApplicationContext.
• Bindy now supports Fixed-Length format message with padding, alignment (Left or Right)
• Improved and fixes some issues with the FTP component.
• Improved and fixed some issues using MultiPartForm with Jetty.
• Add ability to configure Bindy to remove whitespace when binding Numeric positions
• Added option useOriginalBody to OnCompletion
• Fixed issue when using mockito for testing when it uses CGLib proxies
• Fixed issue with @Consume not running in an unit of work to ensure callbacks is invoked when its done
• Routing Slip now uses Expression to define the slip. This is similar to the Recipient List pattern
• The security context can be passed from CXF to other camel Components.
• ManagementAgent settings can now be set using setters from Java, instead of having to use JVM system properties. See tip in Camel JMX wiki page.
• Resequencer in batch mode has two new options allowDuplicates and reverse which allows you to use it for re-ordering messages from JMS queues based on JMSPriority
• Tighten up the ProducerTemplate API a bit, see more details in the section Important changes to consider when upgrading.
• HTTP now better supports sending binary files.
• Fixed problem with using Quartz in OSGi and having Camel applications being hot-deployed which potentially could cause Quartz to stop scheduling in applications which haven't been stopped.
• Fixed issue with pausing and resuming jobs when running Quartz in clustered mode
• Added options on Quartz component to specify location of custom quartz.properties file to load from classpath.
• Upgraded to latest Quartz release 1.8.3.
• Introduced StartupListener to allow components/endpoints/producers/consumers etc. as a listener to be notified when CamelContext have just been started. This allows any custom logic to be executed as a late starter. This ensures Quartz scheduler is only started when all the routes and so forth is started and running.
• Fixed issue with FTP configuring starting directory from uri not accepting an absolute path. In the endpoint uri just define two leading / to indicate absolute, eg "ftp:admin:secret@someserver//absolutepath/foo/bar".
• Added fromRoute to NotifyBuilder.
• Improved the CSV component.
• Fixed issue with Direct endpoint having no consumers if endpoint have been evicted from CamelContext internal LRUCache.
• The RouteBuilder now have simple and xpath expression builder methods out of the box.
• Upgraded to latest release of Scala 2.8.0RC7 in Scala DSL
• camel-hawtdb updated to HawtDB 1.1 picks up several bug fixes that improves stability and performance.
• Fixed issue with splitting files using tokenizer not being able to delete/move file after processing is done on Windows platform.
• maxMessagesPerPoll is now applied eagerly to limit intaking files earlier for the File and FTP components, Thus avoid excessive memory consumption if you poll directories which contains 100.000+ files.
• Added connectTimeout, soTimeout and timeout to FTP so its easier to configure timeouts.
• Consolidated support for per platform disabling of tests across the entire test suite.
• Introduced ProcessorFactory to be able to use a custom factory to be able to manipulate Processor creation process. For example to add additional outputs or manipulate the route model.
• camel-jms now supports Oracle AQ
• Added a Debugger API to be leveraged by 3rd party tooling.
• The beanRef and methodCall DSLs will eager check on startup, the bean reference exists in Registry and the provided method name is a valid method name on the bean as well. This helps to fail fast if end users have a typo in their routes.
• JMX now exposes notifications which listeners can receive.
• Added ExchangeRedeliveryEvent event being emitted when Camel Error Handler attempts a redelivery.
• Properties component can lookup java.util.Properties from the Registry using the ref: prefix.
• Spring Security is upgrade to spring security 3.0.3.RELEASE.

...

Routing Slip now requires using Expression to specify the routing slip header, the XML DSL of Routing Slip is broken.

    <route>
       <from uri="direct:a"/>
       <!--NOTE from Camel 2.4.0, you need to specify the expression element inside of the routingSlip element -->
       <routingSlip ignoreInvalidEndpoints="true">
           <header>myHeader</header>
       </routingSlip>
    </route>

...

...

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

SVN Tag Checkout

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

...