[
https://issues.apache.org/jira/browse/CAMEL-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535200#comment-15535200
]
Claus Ibsen commented on CAMEL-10197:
-------------------------------------
The schema is now
{code}
"timeout": { "kind": "property", "required": "false", "type": "integer",
"javaType": "long", "deprecated": "false", "secret": "false", "defaultValue":
"30000L", "description": "The timeout value to use if block is enabled." }
{code}
Maybe instead of having 30000L as the default value, then the spring-boot maven
plugin can detect that the javaType=long, and then automatic set the L value.
Then we can keep the defaultValue as before without the L.
> 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
> Fix For: 2.18.0
>
>
> 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=172.28.128.4
> {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
(v6.3.4#6332)
