camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ferraro (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10197) camel-spring-boot - Extend the configuration hints to nested properties
Date Mon, 01 Aug 2016 13:59:20 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402074#comment-15402074
] 

Nicola Ferraro commented on CAMEL-10197:
----------------------------------------

I did a fast check and found the following modules (there can be more):

{noformat}
camel-avro
camel-box
camel-braintree
camel-cache
camel-crypto
camel-docker
camel-facebook
camel-ganglia
camel-google-calendar
camel-google-drive
camel-google-mail
camel-kestrel
camel-linkedin
camel-lucene
camel-mail
camel-mina
camel-mina2
camel-nagios
camel-netty
camel-netty4
camel-olingo2
camel-salesforce
camel-smpp
camel-xmlSecurity
camel-zookeeper
--- 
camel-http -> multiple non-annotated beans
camel-http4 -> multiple non-annotated beans
camel-splunk -> 2 levels, first using an interface
camel-stomp -> not sure properties on components are ever read
camel-undertow -> uses complex beans
{noformat}

Using the IDE to generate the getter/setter is definitely easier than changing the maven plugin
(and bind it to a different phase).

> 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
>
> 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)

Mime
View raw message