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 below: 1. Optional xpath expression for filtering 2. Optional processes 3. forwarding of the message to a destination (a different queue or topic) The recipientlist pattern is appropriate. However, it does not seem possible to use the DSL to assemble the route in pieces, as each recipient must be a pipeline of [xpath filter] [0-n processes] and an endpoint. The pieces are contained in a JPA result set, so I cannot piece the route together with DSL (have to loop to get the syntax. I have tried a processor with a producer template, but it does not seem to be reliable. Any hints? Thanks, Jim -- View this message in context: http://www.nabble.com/Data-driven-routing-tp22209256p22209256.html Sent from the Camel - Development (activemq) mailing list archive at Nabble.com.
