Hi Sergey, Messages flow along a route that can be statically or dynamically configured. If I understand you correctly there are 2 things you could look at. One is the dynamic router [1] (and related routing slip [2]) that allows you to make decisions at runtime about how your messages flow. The second is to split your complex route into multiple smaller routes using direct [3] or seda [4] endpoints that would simplify management of your routes (probably).
I hope this helps, Hadrian [1] http://camel.apache.org/dynamic-router.html [2] http://camel.apache.org/routing-slip.html [3] http://camel.apache.org/direct.html [4] http://camel.apache.org/seda.html On Oct 14, 2010, at 1:52 PM, serega wrote: > > Camel documentation shows how to implement > http://camel.apache.org/message-router.html Message Router pattern . In my > case the given examples are not sufficient. I have tens, and may be hundreds > of out endpoints, and complicated routing logic that is dynamic and can > change at runtime. The Processor interface seems like the natural way of > processing messages, but how do I specify the out endpoint in the Processor? > Can someone give me the direction how to solve this problem with Camel? > > Thanks, > Sergey > -- > View this message in context: > http://camel.465427.n5.nabble.com/Custom-Router-tp3212534p3212534.html > Sent from the Camel - Users mailing list archive at Nabble.com.
