[ https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847442#comment-16847442 ]
Claus Ibsen edited comment on CAMEL-13557 at 5/30/19 12:44 PM: --------------------------------------------------------------- Okay big work has been merged on master. There are nice things still to do - support for list/map in keys *DONE* - support for list/map in values *WONT FIX* - auto configure singleton beans from registry on camel components on their nested properties (eg amazon s3 client etc) *DONE* Look at that CXF issue with #xxx where we can make this new support class do the # lookup also. was (Author: davsclaus): Okay big work has been merged on master. There are nice things still to do - support for list/map in keys - support for list/map in values - auto configure singleton beans from registry on camel components on their nested properties (eg amazon s3 client etc) *DONE* Look at that CXF issue with #xxx where we can make this new support class do the # lookup also. > 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)