Hi Claus, do you think it is possible to refactor camel core in this way (to implement a real routing engine)? After the refactorings I already did I am not sure it would work.
Another aproach instead of refactoring would be to first define a new really slim API for components and implement it using the current camel-core. Then we would change each component to use the new API. When all components are switched it will be much easier to change the core as we do not have to refactor all components to make the build work again. We discussed this idea at last Apachecon with Guillaume, Christian Müller and Charles. Then it was mainly in the light of having a small self contained API but I think it would also help with the routing engine. Christian On 19.02.2013 10:31, Claus Ibsen wrote: > > Its been on the Camel 3.0 roadmap for a long time > > Though its heading caption may have been chosen a better wording than > - More flexible routes at runtime > http://camel.apache.org/camel-30-ideas.html > > We had it as target for a long time, but as you said it safter to work > on this in a major release than on the 2.x architecture. > And hence why its not been done yet. > > And in term of the model, then we have missing pieces about the > inteceptors/onExceptions and whatnot. This is also on the roadmap for > Camel 3.0 > - Add OnException, Interceptor, etc. to JAXB model for a > CamelContextDefinition > > -- Christian Schneider http://www.liquid-reality.de Open Source Architect http://www.talend.com
