...

• onComplete(), onFailure() callbacks to UnitOfWork on a Exchange allowing custom code being executed when a Exchange completes
• Much improved OSGi (partly already done )
  • Running ServiceMix 4.0 kernel
  • More documentation and samples
  • Making component/converter discovery use OSGi services when in an OSGi environment
  • All of the bootstrap mechanisms (components, endpoints, converters, registry) should be osgi aware
• improve the DSL
  • to better support polling and explicit MEPs CAMEL-402 CAMEL-486
  • a new schedule DSL for advanced scheduling of polling that can have builder methods (kinda like BAM) so you can:

    Code Block
    schedule().every(5).minute().from("ftp://xxxx).to("bean:processFtpFile")...

• Spring 3.0 support
• Improved JMX
  • Dynamic routing using JMX
  • Pausing consumers using JMX
  • Customization of endpoint options using JMX
  • and a lot more
• self document the custom headers used in the endpoints/components CAMEL-228

Camel 2.x Design

• interceptors should be runtime applied and not woven in at design time - separate design time vs. runtime stuff (jstrachan)
• Restructure of the JAXB creation of routes and whatnot (jstrachan)
• have nice Spring 2 namespace schemas for different endpoints for nicer IDE completion
• pluggable DSL (Hadrian) (Groovy will be able to do this)