[CONF] Apache Camel > Camel 3.0 - Roadmap

[confluence]

Camel 3.0 - Roadmap Page edited by Claus Ibsen Changes (1) ... The internal routing engine should be optimized. See more details at [Camel 2.x Speed optimizations]. h4. More flexible routes at runtime When routes is added in Camel 2.x architecture, global cross cutting concerns such as error handlers, interceptors, onCompletion etc. is applied when the route is added. We need to separate this and have those applied during routing. The {{Channel}} needs to do this and therefore it must be more dynamic than its currently is. And we need to enlist the various global cross cutting concerns by their xxxDefintions in the CamelContext, so we can access them at any time. This allows end users also much more easily to add/remove interceptors, error handlers and whatnot at runtime. And it makes it much easier to add routes generated from JAXB or other sources, as we don't need to prepare or anyhow _mold_ the {{RouteDefinition}} given. See ticket [CAMEL-3024|https://issues.apache.org/activemq/browse/CAMEL-3024] for some details. h4. Support for asynchronous transactions ... Full Content Camel 3.0 roadmap This is a roadmap which details the overall and major goals for Camel 3.0. Fell free to discuss this at the Camel Mailing Lists if you have ideas or feedback. JDK 1.6+ Camel 3.0 should bump the JDK minimum version to 1.6. Camel 1.x/2.x supports JDK 1.5+. Spring 3.x Camel 3.0 should bump the minimum version of Spring to 3.0+. Camel 1.x/2.x supports Spring 2.0+ Routing engine optimization The internal routing engine should be optimized. See more details at Camel 2.x Speed optimizations. More flexible routes at runtime When routes is added in Camel 2.x architecture, global cross cutting concerns such as error handlers, interceptors, onCompletion etc. is applied when the route is added. We need to separate this and have those applied during routing. The Channel needs to do this and therefore it must be more dynamic than its currently is. And we need to enlist the various global cross cutting concerns by their xxxDefintions in the CamelContext, so we can access them at any time. This allows end users also much more easily to add/remove interceptors, error handlers and whatnot at runtime. And it makes it much easier to add routes generated from JAXB or other sources, as we don't need to prepare or anyhow mold the RouteDefinition given. See ticket CAMEL-3024 for some details. Support for asynchronous transactions When using the asynchronous routing engine it would be desirable of transactional context could be propagated to the new threads. This requires the TX manager supports suspend/resume on the TX. G.Nodet have worked a bit on this. See CAMEL-2902. Also see CAMEL-2729. Remove @deprecated @deprecated features, methods, etc. is to be removed. Other ideas Should we switch from commons-logging to slf4j? Change Notification Preferences View Online | View Changes | Add Comment