On Fri, Oct 22, 2010 at 3:58 PM, serega <sergejs.melde...@sybase.com> wrote: > > > Claus Ibsen-2 wrote: >> >> On Fri, Oct 22, 2010 at 3:42 PM, serega <sergejs.melde...@sybase.com> >> wrote: >>> >>> So, how does exactly Dynamic Router work and why does it have "to return >>> null >>> to indicate the end"? >>> Suppose my Dynamic Router returns "file://some_directory". What happens >>> with >>> the message after the call returns? >>> >> >> It goes back to the route until it returns null. >> > > Then, perhaps the Dynamic Router is not exactly what I need. I need the > message to be send > to the specified destination. I guess, I can keep a state in the message and > return null in the second call. > What is the overhead of this loop? >
Sounds like you need recipient list instead http://camel.apache.org/recipient-list.html > Sergey. > -- > View this message in context: > http://camel.465427.n5.nabble.com/Custom-Router-tp3212534p3232289.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
