camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-10197) camel-spring-boot - Extend the configuration hints to nested properties
Date Sat, 03 Sep 2016 10:20:20 GMT


Claus Ibsen commented on CAMEL-10197:

Yes a concern is that there will be gazillions of properties and end users would loose oversight.

Using a Camel component as end user you are intended to use the primary options (eg exposed
by Camel).

Also refs makes sense to configure a property with #foo to refer to a bean with the id foo.
In case the property is not a string, or numeric, boolean type. So you can say camel.component.jetty.httpClient=#myClient

And then you can have a @Bean @Named("myClient") in Spring Boot that creates a HttpClient

> camel-spring-boot - Extend the configuration hints to nested properties
> -----------------------------------------------------------------------
>                 Key: CAMEL-10197
>                 URL:
>             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}
> {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

View raw message