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

Claus Ibsen edited comment on CAMEL-13557 at 5/24/19 9:18 AM:
--------------------------------------------------------------

Got the CXF error fixed.

We should add option on component/endpoint to turn this on|off, as this can 
also be used to configure endpoints with nested options. *DONE*


was (Author: davsclaus):
Got the CXF error fixed.

We should add option on component/endpoint to turn this on|off, as this can 
also be used to configure endpoints with nested options.

> Support for nested properties binding
> -------------------------------------
>
>                 Key: CAMEL-13557
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13557
>             Project: Camel
>          Issue Type: New Feature
>          Components: came-core
>            Reporter: Luca Burgazzoli
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.0.0, 3.0.0-M3
>
>
> As today properties binding does not work for nested objects so assuming I 
> have a class like:
> {code:java}
> class MyComponent {
>     
>     public void setFoo(String foo) {
>         this.foo = foo;
>     }
>     public String getFoo() {
>         return foo;
>     }
>     public void setConfiguration(Configuration conf) {
>         this.conf = conf;
>     }
>     public Configuration getConfiguration() {
>         return conf;
>     }
>     static class Configuration {
>     
>         public void setBar(String bar) {
>             this.bar = bar
>         }
>         public String getBar() {
>             return bar
>         }
>     }
> }
> {code}
> And a set of properties like:
> {code}
> myComponent.foo = "foo"
> myComponent.conf.bar = "bar"
> {code}
> Then only MyComponent.foo will be set but it would be nice if the binding 
> framework could navigate the property using dot notation and set any 
> dependent object.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to