Re: Data-driven routing

2009-02-27 Thread James Strachan
2009/2/27 jbower1950 : > > Thanks to both James and Claus, > > There seem to be several "dynamic" route queries scattered throughout the > web. Both James' example and the new method in 2.0 should be helpful. I am > guessing that I am not alone in trying to solve this problem. Perhaps an > example

Re: Data-driven routing

2009-02-27 Thread jbower1950
Thanks to both James and Claus, There seem to be several "dynamic" route queries scattered throughout the web. Both James' example and the new method in 2.0 should be helpful. I am guessing that I am not alone in trying to solve this problem. Perhaps an example in the docs? Yesterday I got a pro

Re: Data-driven routing

2009-02-27 Thread Claus Ibsen
Hi BTW: We might consider whit Camel 2.0 to add a sample for a real dynamic router where you can create the route in java code and start it for those that are using such thing. This sample uses the dynamic recipient list that is not totally the same: http://camel.apache.org/dynamic-router.html

Re: Data-driven routing

2009-02-27 Thread James Strachan
2009/2/26 jbower1950 : > > I have tried that approach. It was pretty intuitive and made sense. The > problem came when I had two routes from the same source (e.g., a log), one > portion of which I wanted to route to one topic, the other part going to > another topic. It appeared that, using the DSL

Re: Data-driven routing

2009-02-25 Thread jbower1950
I have tried that approach. It was pretty intuitive and made sense. The problem came when I had two routes from the same source (e.g., a log), one portion of which I wanted to route to one topic, the other part going to another topic. It appeared that, using the DSL with two routes, one message wo

Re: Data-driven routing

2009-02-25 Thread James Strachan
2009/2/25 jbower1950 : > > After working through Camel-Spring-ActiveMQ configuration and a DSL approach > I am still struggling with the pieces necessary to achieve dynamic, > data-driven routing for JMS as follows. > > Each "source" (ActiveMQ topic or queue) may have 0-n routes, each defined > bel