Re: typesafe endpoint configuration approach

2013-11-27 Thread Claus Ibsen
I dont think this is a good idea as its too much work for a limited user base. Defining options on an endpoint/component is using pure java getter/setters (aka java bean properties). To have fluent builder configuring with these bean properties is a general problem. So if there is some tool that

Re: typesafe endpoint configuration approach

2013-11-18 Thread ChristianSchaefer
My proposed guess wasn't meant/thought as a replacement for the the string URI configuration of camel. I just thought that it could be a helpful addon especially for Java DSL users. Sure, the endpoint "templates" would require implementation for each endpoint type because they are different in so

Re: typesafe endpoint configuration approach

2013-11-18 Thread ChristianSchaefer
Hi Willem, is there an example of how to "define the Endpoint in the pure Java way,"? Didn't find one.   regards Christian Schäfer Willem.Jiang [via Camel] schrieb am 2:34 Montag, 18.November 2013: Hi,   I’m not a not a big fan of this type safe endpoint configuration. As the endpoint

Re: typesafe endpoint configuration approach

2013-11-17 Thread Willem jiang
Hi, I’m not a not a big fan of this type safe endpoint configuration. As the endpoints are different from each other, you cannot define a unified fluent API for all the endpoints. But Camel does support to define the Endpoint in the pure Java way, but it is not as easy as using the URI to set