Re: REST DSL Component, Consumer and Endpoint properties as Strings

2015-09-21 Thread Sergey Beryozkin
This is helpful, thanks Cheers, Sergey On 21/09/15 11:55, Claus Ibsen wrote: You can configure complex objects using the lookup notation using #nameOfBean. This is how you would configure Camel endpoints usually. The rest-dsl is for both java and xml and the syntax is for using values that are

Re: REST DSL Component, Consumer and Endpoint properties as Strings

2015-09-21 Thread Claus Ibsen
You can configure complex objects using the lookup notation using #nameOfBean. This is how you would configure Camel endpoints usually. The rest-dsl is for both java and xml and the syntax is for using values that are possible in both worlds. Its rest configuration is also for simpler and lighter

REST DSL Component, Consumer and Endpoint properties as Strings

2015-09-18 Thread Sergey Beryozkin
Hi I've noticed that when setting component, consumer, endpoint properties in REST DSL, once can only use String value (example, MapString>), while in the related component/consumer/endpoint code there's an expectation that the values are Objects, Map. Having String values can be a bit of a b