Re: [DISCUSS] Meta model

2019-07-25 Thread Guillaume Nodet
Le jeu. 25 juil. 2019 à 20:28, Zoran Regvart a écrit : > Hi Guillaume, > since we're all piling up on you :) One more thing I'd like you to > consider :) > > I find Velocity templates a bit brittle and hard to maintain, would > you consider a Java code generator to create the Java source code? >

Re: [DISCUSS] Meta model

2019-07-25 Thread Jean-Baptiste Onofré
Hi Model driven makes sense. I like velocity but I understand Zoran's comment. Maybe we can imagine some pluggable: pojo describing model and binding. Regards JB Le 25 juil. 2019 à 20:28, à 20:28, Zoran Regvart a écrit: >Hi Guillaume, >since we're all piling up on you :) One more thing I'd li

Re: [DISCUSS] Meta model

2019-07-25 Thread Zoran Regvart
Hi Guillaume, since we're all piling up on you :) One more thing I'd like you to consider :) I find Velocity templates a bit brittle and hard to maintain, would you consider a Java code generator to create the Java source code? I've found JavaPoet[1] pretty nifty in this regard. I've used it for

Re: [DISCUSS] Meta model

2019-07-25 Thread Luca Burgazzoli
Couple of questions: - how does this play with external components ? - what about annotations we have now i.e. for endpoints ? I found particularity useful that types, enum values and so one are taken from the java code --- Luca Burgazzoli On Thu, Jul 25, 2019 at 12:04 PM Claus Ibsen wrote: >

Re: [DISCUSS] Meta model

2019-07-25 Thread Claus Ibsen
Hi Btw a follow up question. Would we be able to get to a point where all the model classes (xxxDefinition and helpers etc) can be dropped at runtime, eg for camel-quarkus optimization? And also the refiers as they are the builder from model -> processor. Well what you experiment with is surely

Re: [DISCUSS] Meta model

2019-07-25 Thread Claus Ibsen
On Thu, Jul 25, 2019 at 11:28 AM Guillaume Nodet wrote: > > Le jeu. 25 juil. 2019 à 10:47, Claus Ibsen a écrit : > > > Hi > > > > Good to see more experiments, but as others have said in this mail > > thread, its too overwhelming to dive into and understand. > > > > Yes, I definitely get that, es

Re: [DISCUSS] Meta model

2019-07-25 Thread Guillaume Nodet
Your point is really interesting. However, I think one of the main problem right now is that the metamodel information is spread in the whole source tree (some bits in camel-core, and lots in the various components). This leads to a lot of hacks and round trips in the build system (copying json f

Re: [DISCUSS] Meta model

2019-07-25 Thread Guillaume Nodet
Le jeu. 25 juil. 2019 à 10:47, Claus Ibsen a écrit : > Hi > > Good to see more experiments, but as others have said in this mail > thread, its too overwhelming to dive into and understand. > Yes, I definitely get that, especially as it's still work in progress. On the java dsl side, the goal is

Re: [DISCUSS] Meta model

2019-07-25 Thread Zoran Regvart
Hi Guillaume & Cameleers, I like that there's an effort to make the code more maintainable. I do however feel that the source of truth is best kept in the Java code, and perhaps this new model can be generated from that. I understand the need for having a single strictly typed source of truth. Cou

Re: [DISCUSS] Meta model

2019-07-25 Thread Claus Ibsen
Hi Good to see more experiments, but as others have said in this mail thread, its too overwhelming to dive into and understand. So what I can see is that the model is now more "coded" in velocity vm and xml xslt files, than what we had before with the java model classes with JAXB annotations. Als

Re: [DISCUSS] Meta model

2019-07-25 Thread Onder SEZGIN
Hi, yes some examples to describe these new features would be great. There are tones of changes which is a bit hard to follow at this stage (at least for me) On Wed, Jul 24, 2019 at 4:17 PM Andrea Cosentino wrote: > Yeah, a concrete example of what has been done could be useful to better > und

Re: [DISCUSS] Meta model

2019-07-24 Thread Andrea Cosentino
Yeah, a concrete example of what has been done could be useful to better understand Il mer 24 lug 2019, 17:11 Luca Burgazzoli ha scritto: > I Guillaume, > > I think it is a little bit hard to figure out what's happening looking at > the code changes as it is quite a huge list of changed file :)

Re: [DISCUSS] Meta model

2019-07-24 Thread Luca Burgazzoli
I Guillaume, I think it is a little bit hard to figure out what's happening looking at the code changes as it is quite a huge list of changed file :) Maybe having some concrete examples or an examples of what things will look like could help to have a better understanding and giove more options to

[DISCUSS] Meta model

2019-07-24 Thread Guillaume Nodet
Hey everyone ! The last weeks, I've spend quite some time working on a camel metamodel. The idea is to invert the way things are built in camel so instead of generating the metamodel from the classes, the metamodel would be maintained manually and used to generate a bunch of things. This would br