[
https://issues.apache.org/jira/browse/CAMEL-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152205#comment-16152205
]
Claus Ibsen commented on CAMEL-11707:
-------------------------------------
I think if you can configure this today in regular Camel then it should be a
1:1 in spring boot as well.
So I dont (yet) see the point of hiding options in spring-boot which you can
use in regular Camel.
I dont like when there is too much difference, the power of Camel is that XML,
Java, JEE, Spring Boot et all is almost similar how you use Camel
EIPs/components/routes etc.
Can you explain more about this and maybe provide some examples?
> 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)
