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 can generate builder apis from getter/setters then that would be compelling. To maintain all the code ourselves is too much work as we have 150+ components. On Tue, Nov 19, 2013 at 12:29 AM, ChristianSchaefer <syrious3...@yahoo.de> wrote: > 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 some aspects. > > However, referring to the feedback a contribution is not really wanted in > this case. > > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/typesafe-endpoint-configuration-approach-tp5743391p5743469.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
