I thought about that, thing is I will know that at runtime only.
James.Strachan wrote:
>
> 2008/9/11 Seb- <[EMAIL PROTECTED]>:
>>
>> Hi Hadrian,
>> Sure I have access to Exchange/Body/...
>> But I was looking for something like this:
>>
>> from("activemq:Foo").recipientList().methodCall("someBean", "myMethod",
>> "some", "parameters", ...);
>
> Why not use Spring to create an instance of your bean injected with
> whatever parameters you want.
>
> from("activemq:Foo").recipientList().methodCall("someBeanWithParams1",
> "myMethod");
> from("activemq:Foo").recipientList().methodCall("someBeanWithParams2",
> "myMethod");
>
>
> etc. i.e. you just need to create a name for each set of parameters
> you need. Or create a FactoryBean to inject custom properties
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://open.iona.com
>
>
--
View this message in context:
http://www.nabble.com/Routing-depending-on-a-Service-tp19393604s22882p19451800.html
Sent from the Camel - Users mailing list archive at Nabble.com.
