[jira] [Comment Edited] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847442#comment-16847442
]
Claus Ibsen edited comment on CAMEL-13557 at 5/30/19 6:38 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. *DONE*
was (Author: davsclaus):
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.
> 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)
[jira] [Comment Edited] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Comment Edited] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847442#comment-16847442
]
Claus Ibsen edited comment on CAMEL-13557 at 5/28/19 3:17 PM:
--
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*
was (Author: davsclaus):
Okay big work has been merged on master.
There are two nice things still to do
- support for list/map in keys
- auto configure singleton beans from registry on camel components on their
nested properties (eg amazon s3 client etc) *DONE*
> 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)
[jira] [Comment Edited] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848055#comment-16848055
]
Claus Ibsen edited comment on CAMEL-13557 at 5/28/19 3:17 PM:
--
Okay there are a number of test failures which I didnt spot locally. I will
take a look later this weekend. *DONE*
https://builds.apache.org/job/Camel/job/master/lastCompletedBuild/testReport/
was (Author: davsclaus):
Okay there are a number of test failures which I didnt spot locally. I will
take a look later this weekend.
https://builds.apache.org/job/Camel/job/master/lastCompletedBuild/testReport/
> 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)
[jira] [Comment Edited] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847442#comment-16847442
]
Claus Ibsen edited comment on CAMEL-13557 at 5/28/19 3:17 PM:
--
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.
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*
> 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)
[jira] [Comment Edited] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847442#comment-16847442
]
Claus Ibsen edited comment on CAMEL-13557 at 5/24/19 12:26 PM:
---
Okay big work has been merged on master.
There are two nice things still to do
- support for list/map in keys
- auto configure singleton beans from registry on camel components on their
nested properties (eg amazon s3 client etc) *DONE*
was (Author: davsclaus):
Okay big work has been merged on master.
There are two nice things still to do
- support for list/map in keys
- auto configure singleton beans from registry on camel components on their
nested properties (eg amazon s3 client etc)
> 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)
[jira] [Comment Edited] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Comment Edited] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845840#comment-16845840
]
Claus Ibsen edited comment on CAMEL-13557 at 5/22/19 12:47 PM:
---
Need to optimize this a bit as consumer.xxx options are set also on various
instances where we afterwards normally would extract consumer.xxx options and
set them specially.
was (Author: davsclaus):
Need to optimize this a bit as consumer.xxx options are set 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)
[jira] [Comment Edited] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845776#comment-16845776
]
Luca Burgazzoli edited comment on CAMEL-13557 at 5/22/19 11:18 AM:
---
[~davsclaus] Would be very nice to have such functionality extracted in a set
of functions, maybe a new helper. The reason is that in camel-k we may need it
outside main to configure other aspect of the runtime
was (Author: lb):
Would be very nice to have such functionality extracted in a set of functions,
maybe something new, the reason is that in camel-k we may need to use it
outside main to configure other aspect fo the runtim
> 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)
