Hi again, Konrad! One thing that came out my mind when starting the new version: metatype resources are... metatype resources, components with properties, while I wanted to add the power to understand if the component is an HTTP entry point, a Filter and a Service - this should make the tool more extensible, without parsing strings :)
Would it make sense? Many thanks in advance! ~Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Fri, Aug 3, 2018 at 11:03 AM Simone Tripodi <[email protected]> wrote: > Hi there Konrad, > thank you su much for your interest, very appreciated! > > >> What about instead acting on top of the generated component definitions >> or metatype resources? That way you would be independent of how they have >> been generated? >> Konrad > > > I have also an implementation of this policy, but that approach didn't let > me really satisfied: IMHO the direct access to the source code, handling > proper types and so on, keeps the tool source code cleaner and easier to > read/maintain, rather than having an interpreter which deals with multiple > string. > > Maybe is a matter of tastes, but I see you point: what I am proposing is a > Swiss Knife while a single Sword could cut them all. > I'll think twice about that :) > > Thanks and all the best, > ~Simo > > http://people.apache.org/~simonetripodi/ >
