THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- remove the use of generics on Component, Exchange, Producer, Consumer to reduce the need to copy exchanges CAMEL-872 CAMEL-507
- enhance the Expression/Predicate APIs to allow the required type to be passed in
- remove @deprecated code
- improvement of discovery of class resources in OSGi bundles CAMEL-775
- cleanup Pipeline, BeanInfo (the algorithm to select right method to invoke by bean component)
- UUID generator to be file friendly (eg zapping / and : chars)
- Enhance functionality of Quartz component to cover non-volatile jobs, clustering (including connecting to an existing job store). Look into using Spring's Quartz support as a foundation (paricularly SchedulerFactoryBean).
- Dealing with streams and minimizing copy performance (jstrachan)
Nice to haves
- self document the custom headers used in the endpoints/components CAMEL-228
- Model objects toString(), label, shortName and description aligned and usable from Tracer/Visual Tooling etc.
Camel 2.
...
1 Design
Main features
- Much improved OSGi
- 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
- Spring 3.0 supporthave nice Spring 2 namespace schemas for different endpoints for nicer IDE completion
- Improved JMX
- Dynamic routing using JMX
- Pausing consumers using JMX
- Customization of endpoint options using JMX
- and a lot more
Camel 2.x Design
- have nice Spring 2 namespace schemas for different endpoints for nicer IDE completion
- pluggable DSL (Hadrian)Spring 3.0 support