Hi JIRA: https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-14568
I am working on having the tooling detect nested configuration options on components (like we do for endpoints, via @UriParams) and include these extra options in the metadata such as .json and also the generated configurer classes, and the component-dsl. And therefore also in the adoc documentation. This means that when all the components is regen then many source code files are updated as all of these new options are included. This makes configuring Camel components more attractive as you can now easier configure all these options individually, via .properties files, or component-dsl etc. There was already support for this via camel-spring-boot as we had SB auto configurer source code generated that included those in Camel 2.x as well. But with this change we bring the same level all across. And then after this we can look at making SB use the configurer classes as well for non-reflection configuration. Some components may need to change slightly as they may have duplicate options as before some options that was on the configuration class was not exposed on component level, and so a setter/getter was manually added as a duplicate. This will now clash and the duplicate will be manually removed. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
