Claus Ibsen commented on CAMEL-10197:

Yeah its a bit drastic change this ticket / code commits.

We should blaclist some of the core Camel types such as HeaderFilterStrategy 
which is now marked as nested but it has no options to configure (there is no 
getter/setter on it etc.). 

> camel-spring-boot - Extend the configuration hints to nested properties
> -----------------------------------------------------------------------
>                 Key: CAMEL-10197
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10197
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-spring-boot
>            Reporter: Nicola Ferraro
>            Assignee: Dhiraj Bokde
> Support for spring-boot configuration allows users to configure the component 
> properties but does not give any hint on nested properties.
> There are many components that declare properties on nested beans.
> Eg. camel-docker has only one property named _configuration_ .  I found this 
> pattern in components that allow users to specify a default value on the 
> component and override it on each endpoint, if necessary.
> Setting the property:
> {code}
> camel.component.docker.configuration.host=
> {code}
> allows a user to specify the docker host, but the tooling does not give 
> suggestions about that property.
> A way to allow the users to view the nested properties is using the 
> {{NestedConfigurationProperty}} annotation on the spring-boot configuration 
> class. The spring-boot inspector will scan the nested class for properties.
> The drawback is that the javadoc is not read from setters. Another drawback 
> is that we will be using a different approach respect to the "read-the-json" 
> one.
> We need to figure out how to add these properties.

This message was sent by Atlassian JIRA

Reply via email to