Hi Okay done with some more work.
So we now have started to splitup into base vs engine. Where the intention is that whats in -engine is related to the full routing engine, with routes, DSL, model, and everything. And then the base is minimalistic. However the classes in base-engine (camel.impl.engine) has not been analyzed whether that can be in base vs base-engine. But they are internal, so they should be able to be moved in the future also. On Sun, Oct 25, 2020 at 4:16 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > > Hi > > Some more work on the way. Now the camel-core-model, > camel-core-reifier are separated from camel-base and are independent. > After that its camel-core-processor to see if we can get it > independent from camel-base. There are some base processors that may > belong in camel-base. > And then leave camel-core-processor for the EIP implementations. But > need to find a balance. > > Having that last thing we are much closer on having the model and > routing engine (RouteBuilder) / XML DSL et all as optional. So Camel > can be very light for some use-cases where you dont need routing or > the DSL. > > On Sun, Oct 25, 2020 at 12:32 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > > > > Hi > > > > I got further and now the processors are moved into camel-core-processor. > > > > Which means we have model, reifier and processors splitted up. > > There is a little bit to do in the other modules to not depend on > > camel-base but they can use camel-core-processor instead. > > > > Also the processors can be split up into eip (or model) processors and > > base processors. Then we are closer to also offer a simple camel > > context > > that has no route builder, no model, routing engine etc. But for a > > tiny runtime usecases where its okay to just use camel as a producer > > or consumer template without routing. > > > > > > On Sat, Oct 24, 2020 at 7:26 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > > > > > > Hi > > > > > > I got started this weekend on more modularization of core, where we > > > can move out model and reifier from the engine, so they are separated. > > > https://issues.apache.org/jira/browse/CAMEL-15740 > > > > > > I wanted to do this over the weekend where the activity on the master > > > branch is lower than week days. > > > > > > I have the work done for the core repo, but would possibly need small > > > tweaks in camel-karaf (for its blueprint xsd generator) and maybe also > > > in spring-boot. > > > > > > With this moduralization we are getting closer to, and would make it > > > easier in the future to be able to do more build time optimizations > > > and class unloading / dead code elimination. > > > > > > My hope is we get to a point where we can offer a full build time > > > optimization that takes the DSL and via the model and reifiers build > > > the runtime processors (routes) and then at *real* runtime we can drop > > > all the model and reifier all together. > > > > > > Having them separated and in their own module / JAR makes this work > > > easier. > > > > > > There is still some work as CamelContext has a ModelCamelContext / > > > Model that we somehow need to find a way to drop in an extreme > > > optimization. > > > > > > > > > > > > -- > > > Claus Ibsen > > > ----------------- > > > http://davsclaus.com @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > -- > > Claus Ibsen > > ----------------- > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
