I would have a Manager class with a method call(String bean, String...
parameters)
And this manager would be responsible for the real call to the bean (I don't
want to call the beans directly). So I would have something like this:
from("activemq:Foo").recipientList().methodCall("myManager", "call",
"beanX", "parameters", ...);
And myManager would delegate the call to beanX.
Maybe there is a cleaner way to do this ? (Delegators?...)
James.Strachan wrote:
>
> Could you give an example of some pseudocode you'd like to use?
>
> 2008/9/12 James Strachan <[EMAIL PROTECTED]>:
>> 2008/9/12 Seb- <[EMAIL PROTECTED]>:
>>>
>>> I thought about that, thing is I will know that at runtime only.
>>
>> Any runtime knowledge can be wrapped up in a factory bean; or you can
>> extract data from the message and use that to invoke a factory bean?
>>
>> --
>> James
>> -------
>> http://macstrac.blogspot.com/
>>
>> Open Source Integration
>> http://open.iona.com
>>
>
>
>
> --
> 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-tp19393604s22882p19452072.html
Sent from the Camel - Users mailing list archive at Nabble.com.
