[
https://issues.apache.org/jira/browse/CAMEL-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152290#comment-16152290
]
Luca Burgazzoli commented on CAMEL-11707:
-----------------------------------------
It was not meant to reduce what you can do with spring boot but more to have a
way to fix code generation limitations when needed, i.e. as the code generation
does not properly handle class hierarchies, it generates an incomplete
properties binding but one can't change the generated code so one way is to use
customizers but we need a way to tell the spring boot code generator not to
handle some of the properties to avoid conflicts. In some cases the code
generator annotates beans with @NestedConfigurationProperty but for some bean
may not be directly instantiated so the spring boot binding may fail.
> spring boot code generation: there should be a way to exclude some properties
> from the code generation
> ------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-11707
> URL: https://issues.apache.org/jira/browse/CAMEL-11707
> Project: Camel
> Issue Type: Improvement
> Components: tooling
> Reporter: Luca Burgazzoli
> Fix For: 2.20.0
>
>
> As today every property is exposed to spring boot auto configuration
> processor but sometimes you may want to hide some or them as they may be
> supposed to be used only internally or because you want to write your own
> code to manage complex configurations.
> As this may also be needed to hide info from the catalog, we may have
> something like:
> {code}
> @Metadata(key = "ignore", value = "true", labels = "spring-boot,catalog")
> {code}
> Or have specific annotations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
