Hello, Thanks for your participation in users@camel!
Even if we provided a way to set dynamic parameters as part of the URI – and have Camel channel those downstream from the producer to the consumer – how would the endpoints/processors sitting behind the SEDA / VM / Direct consumers acquire access to them? What do you have in mind exactly? Bear in mind that all Camel elements (components, processors, EIPs, etc.) revolve around the Camel Exchange/Message API, consisting of generic concepts such as Exchanges, Messages, Headers, Properties, Exception, etc. Regards, *Raúl Kripalani* Apache Camel PMC Member & Committer | Enterprise Architect, Open Source Integration specialist http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Sun, Nov 3, 2013 at 10:53 PM, alapaka <alap...@rocketmail.com> wrote: > G'day all; > > Is there a way to pass parameters (i.e. like a function call) to a direct / > seda / vm consumer endpoint? > > Setting headers works, but I reckon it would be much cleaner and clearer if > we could pass actual parameters as part of the call to the endpoint, either > as part of the URI or as child elements of the <to> element. Even better > would be if we could define parameters as optional/required on the consumer > endpoint, but simply being able to pass them without resorting to headers > etc.. would be much better imho. > > I am running version 2.10.7, and setting 'unknown' properties on the URI > query string results in errors. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Passing-parameters-to-a-direct-seda-vm-endpoint-tp5742567.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
