Camel 2.1 Design

Main features

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)
minimizing copy performance
onComplete(), onFailure() callbacks to UnitOfWork on a Exchange allowing custom code being executed when a Exchange completes
OSGi
Much improved OSGi (partly already done ) willem)
- Integration test using real OSGi platform in Camel codebase
- 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
- Making component/converter discovery use OSGi services when in an OSGi environment
- Making ObjectHelper.loadClass aware of OSGi environment
- More documentation and samples
  DSL
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")...
  Other
Spring 3.0 support
Improved Dynamic Route Manipulation
- Dynamic routing add/edit/stop/remove
- Pausing consumers
- Customization of endpoint options
- and a lot more
self document the custom headers used in the endpoints/components CAMEL-228

...